-
Enhancement
-
Resolution: Done
-
Minor
-
19.0.0.Beta5
-
User Experience
This bug occurs with an .ear file deployment that contains .war subdeployments.
When trying to "ls -l" the subsystems in the .ear deployment, the CLI's autocomplete is suggesting subsystems under the .ear deployment that don't exist and should only be under the .war subdeployments. Doing an actual "ls -l" command on the non-existent subsystems of the .ear file gives a "not found" error, as it should:
[standalone@localhost:9990 /] ls -l /deployment=EnterpriseHelloWorld.ear/subsystem=<TAB> batch-jberet datasources ejb3 jaxrs jpa logging resource-adapters undertow webservices
[standalone@localhost:9990 /] ls -l /deployment=EnterpriseHelloWorld.ear/subsystem=undertow {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => "WFLYCTL0216: Management resource '[ (\"deployment\" => \"EnterpriseHelloWorld.ear\"), (\"subsystem\" => \"undertow\") ]' not found"}}
When it comes to the subdeployments, everything works as it should:
[standalone@localhost:9990 /] ls -l /deployment=EnterpriseHelloWorld.ear/subdeployment=HelloWorld<TAB> HelloWorldFirst.war HelloWorldSecond.war
[standalone@localhost:9990 /] ls -l /deployment=EnterpriseHelloWorld.ear/subdeployment=HelloWorldFirst.war/subsystem=<TAB> batch-jberet datasources ejb3 jaxrs jpa logging resource-adapters undertow webservices
[standalone@localhost:9990 /] ls -l /deployment=EnterpriseHelloWorld.ear/subdeployment=HelloWorldFirst.war/subsystem=undertow ATTRIBUTE VALUE TYPE active-sessions 0 INT context-root /HelloWorldFirst STRING expired-sessions 0 INT highest-session-count 0 INT max-active-sessions -1 INT rejected-sessions 0 INT server default-server STRING session-avg-alive-time 0 INT session-max-alive-time 0 INT sessions-created 0 INT virtual-host default-host STRING
- clones
-
JBEAP-19896 [GSS](7.4.z) WFCORE-5852 - CLI autocomplete suggests non-existent subsystems
- Closed
- is blocked by
-
WFLY-16158 Deployment submodel should be runtime
- Closed
-
WFCORE-5853 Deployment SubModel for logging should be runtime only
- Closed
- is related to
-
WFCORE-4183 ReadResourceHandler returns runtime values stored in the DMR model even if include-runtime=false
- Resolved
-
WFCORE-3432 Correct ManagementResourceRegistration runtime-only metadata
- Resolved