Consider seperate namespace for management model ------------------------------------------------ Key: AS7-2234 URL: https://issues.jboss.org/browse/AS7-2234 Project: Application Server 7 Issue Type: Task Components: Domain Management Reporter: Thomas Diesler Assignee: Brian Stansberry Related to [Finding out what version of the Detyped API a client is dealing with|http://lists.jboss.org/pipermail/jboss-as7-dev/2011-October/004206.html] we currently have {code} [standalone@localhost:9999 /] /subsystem=osgi:read-resource-description { "outcome" => "success", "result" => { "description" => "The the OSGi subsystem configuration.", "head-comment-allowed" => true, "tail-comment-allowed" => true, "namespace" => "urn:jboss:domain:osgi:1.0", "attributes" => { "activation" => { "description" => "Activation flag for the OSGi subsystem. Possible values: lazy, eager.", "type" => STRING, "default" => "LAZY", "access-type" => "read-write", "restart-required" => "no-services", "storage" => "configuration" }, "startlevel" => { "description" => "The current Start Level of the OSGi Framework. Changing this value will change the start level of the Framework accordingly. ", "type" => INT, "access-type" => "read-write", "restart-required" => "no-services", "storage" => "runtime" } }, "children" => { "configuration" => {"description" => "A configuration entry."}, "property" => {"description" => "A framework property."}, "capability" => {"description" => "A framework capability."}, "bundle" => {"description" => "Runtime bundle information."} } } } {code} The namespace definition of the model {code} "namespace" => "urn:jboss:domain:osgi:1.0", {code} is that of the XML representation - worse, it is that of an outdated XML representation. Some subsystems do not define a namespace for their model at all. I suggest to define an individual namespace per subsystem with some compatibility rule encoded within. Management clients can then decide whether and to what extend they can manage that subsystem. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira