-
Bug
-
Resolution: Done
-
Blocker
-
None
-
None
-
None
The result of a composite operation which contains a read-resource operation with wildcards is missing the address node.
WildFly 9
[domain@localhost:9990 /] batch [domain@localhost:9990 / #] /server-group=*/deployment=*:read-resource [domain@localhost:9990 / #] run-batch --verbose { "outcome" => "success", "result" => {"step-1" => { "outcome" => "success", "result" => [{ "address" => undefined, "outcome" => undefined, "result" => { "enabled" => false, "name" => "jboss-as-login.war", "runtime-name" => "jboss-as-login.war" } }] }}, "server-groups" => undefined }
WildFly 8.2.0
[domain@localhost:9990 /] batch [domain@localhost:9990 / #] /server-group=*/deployment=*:read-resource [domain@localhost:9990 / #] run-batch --verbose { "outcome" => "success", "result" => {"step-1" => { "outcome" => "success", "result" => [{ "address" => [ ("server-group" => "main-server-group"), ("deployment" => "test-application.war") ], "outcome" => undefined, "result" => { "enabled" => false, "name" => "test-application.war", "runtime-name" => "test-application.war" } }] }}, "server-groups" => undefined }
Executing the read-resource op itself yields the same result for WildFly 8.2.0.Final and 9