V3: Admin CLI Improvements This document is part of V3AdministrationImprovements. This is what we'd like to see in admin console. %%sortable
| Feature-ID |
Requirement |
Priority |
Comments |
Issue Link |
Eng Response |
| CLI-1 |
Feature parity between Admin CLI and administration console |
P1 |
With some notable exceptions, such as console common tasks and "start-domain" CLI command. |
4278 4279 4280 4281 4282 |
Yes. We will continue to offer CLI support with notable exceptions. |
| CLI-2 |
GlassFish V2 stopserv command to kill a hung process as in Application Server 7 |
P2 |
*Very* heavily loaded systems had a hard time shutting down an instance. This issue has been addressed to a large degree by not spawning another JVM to shut down an instance. If reports of this issue continue then this requirement should be followed. |
|
Yes. |
| CLI-3 |
Edge case where list-node-agents command after delete-node-agent continues to show deleted node-agent |
P2 |
|
|
Yes. Isn't this a bug? |
| CLI-4 |
Support "pathnames" to MBeans in CLI |
P1 |
Critical to supporting arbitrary MBeans/modules generically, allowing access to all attributes of all MBeans: config, monitoring, runtime, anything.<br>See GlassFish V3 Path Name and CLI Specification |
na |
TBD |
| CLI-5 |
Support file system analogy for MBeans |
P2 |
Ease of use (file system analogy) for pathnames. 'cd', 'ls', 'pwd', etc. <br>See GlassFish V3 Path Name and CLI Specification |
na |
TBD |
| CLI-6 |
Support generic create/delete of config |
P2 |
With pathnames (CLI-4), it should be possible to create and delete any sub-element of configuration.<br>See GlassFish V3 Path Name and CLI Specification |
na |
TBD |
| CLI-7 |
Separate meta options |
P1 |
Use 'cvs' style meta options that precede the sub-command so as to avoid option-name conflicts as well as to make it clear the security connectivity options vs those to be delivered to the command itself. This is important for a generic system.<br>See GlassFish V3 Path Name and CLI Specification |
na |
TBD |
|
