Back to bug 1007831
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Petr Sakař | 2013-09-13 12:10:29 UTC | Target Release | --- | EAP 6.2.0 |
| Petr Sakař | 2013-09-13 12:13:24 UTC | Summary | CLI GUI - add operation for webservices client-config fails | CLI GUI - add operation for webservices client-config and endpoint-config fails |
| Alessio Soldano | 2014-02-14 11:56:36 UTC | Assignee | asoldano | ssilvert |
| Petr Sakař | 2014-03-20 10:28:01 UTC | Priority | unspecified | medium |
| Target Release | EAP 6.2.0 | EAP 6.3.0 | ||
| Stan Silvert | 2014-03-21 11:47:26 UTC | CC | brian.stansberry | |
| Component | Web Services | CLI | ||
| QA Contact | rsvoboda | pkremens | ||
| Petr Sakař | 2014-03-21 12:53:38 UTC | Status | NEW | ASSIGNED |
| Assignee | ssilvert | olubyans | ||
| Kabir Khan | 2014-03-24 13:24:19 UTC | CC | kkhan | |
| Kabir Khan | 2014-03-24 15:40:40 UTC | Status | ASSIGNED | MODIFIED |
| Target Milestone | --- | DR6 | ||
| Paul Gier | 2014-03-25 21:07:48 UTC | Status | MODIFIED | ON_QA |
| Petr Kremensky | 2014-04-01 11:14:35 UTC | Status | ON_QA | VERIFIED |
| Alexey Loubyansky | 2014-06-03 09:22:13 UTC | Doc Text | Cause: 'add' operation which didn't take any arguments was treated as an operation that didn't require any input from the user of the CLI GUI. Consequence: the user would be offered to execute the operation w/o providing the required argument 'name' which would lead a failure. Fix: 'add' operation w/o arguments is now treated by the GUI interface logic as one having required 'name' argument. Result: before allowing the user to execute 'add' operation which in the management model description doesn't require any argument, the user will be offered to provide the required 'name' argument. |
|
| Scott Mumford | 2014-06-05 02:12:29 UTC | CC | smumford | |
| Doc Text | Cause: 'add' operation which didn't take any arguments was treated as an operation that didn't require any input from the user of the CLI GUI. Consequence: the user would be offered to execute the operation w/o providing the required argument 'name' which would lead a failure. Fix: 'add' operation w/o arguments is now treated by the GUI interface logic as one having required 'name' argument. Result: before allowing the user to execute 'add' operation which in the management model description doesn't require any argument, the user will be offered to provide the required 'name' argument. | In previous releases of JBoss EAP 6 an 'add' operation which did not have any arguments was treated as an operation that did not require any input from the user of the CLI GUI. This caused the user to be able to execute the operation without providing the required argument 'name' which would lead to a failure. In this release the 'add' operation without arguments is now treated by the GUI interface logic as one having required 'name' argument. Now, before allowing the user to execute an 'add' operation which in the management model description doesn't require any argument, the user will be prompted to provide the required 'name' argument. |
||
| John Skeoch | 2014-06-18 07:21:05 UTC | CC | nobody | |
| Scott Mumford | 2014-06-24 02:28:10 UTC | Doc Text | In previous releases of JBoss EAP 6 an 'add' operation which did not have any arguments was treated as an operation that did not require any input from the user of the CLI GUI. This caused the user to be able to execute the operation without providing the required argument 'name' which would lead to a failure. In this release the 'add' operation without arguments is now treated by the GUI interface logic as one having required 'name' argument. Now, before allowing the user to execute an 'add' operation which in the management model description doesn't require any argument, the user will be prompted to provide the required 'name' argument. | In previous releases of JBoss EAP 6 an 'add' operation which did not have any arguments was treated as an operation that did not require any input from the user of the CLI GUI. This caused the user to be able to execute the operation without providing the required argument 'name' which would lead to a failure. In this release the 'add' operation without arguments is now treated by the GUI interface logic as one having required 'name' argument. Now, before allowing the user to execute an 'add' operation which in the management model description does not require any argument, the user will be prompted to provide the required 'name' argument. |
| mark yarborough | 2014-06-28 15:30:13 UTC | Status | VERIFIED | CLOSED |
| Resolution | --- | CURRENTRELEASE | ||
| Last Closed | 2014-06-28 11:30:13 UTC |
Back to bug 1007831