[jboss-jira] [JBoss JIRA] (AS7-2234) Consider separate namespace for management model
[
https://issues.jboss.org/browse/AS7-2234?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry updated AS7-2234:
----------------------------------
Fix Version/s: 7.1.0.Final
(was: 7.1.0.CR1)
Moving to Final as this is not really critical for CR1. I'd like to get it in though
and will pull it back into CR1 if possible.
My intent was to add an overloaded method to ExtensionContext:
SubsystemRegistration registerSubsystem(String name, int majorVersion, int minorVersion)
throws IllegalArgumentException, IllegalStateException;
and deprecate the existing method.
The provided information will go into a resource that's associated with the extension
resource -- from it you can get information about available subsystems provided by the
extension. This stuff would be a detail. An "undefined" value would be allowed
(for subsystems written against the deprecated registerSubsystem(name) method.) It would
also expose the registered xml namespaces.
The major/minor version of the core management API would be exposed as attributes on the
domain/host/server root resources.
Consider separate 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
Priority: Blocker
Fix For: 7.1.0.Final
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