Bug 1049102

In previous versions of JBoss EAP 6, the management operation handler used to determine the status of a deployment was using the deployment name to find the deployment service instead of using its runtime-name. As a result, if a deployment had a runtime-name that was different from its management name, an attempt to read its "status" attribute would result in a response of `No metrics available`. For example: ---- [standalone@localhost:9999 /] deploy /home/ABC.ear --name=ABC.ear --runtime-name=XYZ.ear [standalone@localhost:9999 /] /deployment=ABC.ear:read-attribute(name=status) { "outcome" => "success", "result" => "no metrics available" } ---- In this release of the product, the management handler uses the runtime-name when looking up the deployment service which ensures the status is correctly returned. The response from the above example is now: ---- [standalone@localhost:9999 /] /deployment=ABC.ear:read-attribute(name=status) { "outcome" => "success", "result" => "OK" } ----