[
https://jira.jboss.org/jira/browse/JBAS-6688?page=com.atlassian.jira.plug...
]
Ian Springer updated JBAS-6688:
-------------------------------
Summary: expose ManagedProperties representing ObjectNames as
SimpleMetaType.STRINGs rather than
ImmutableCompositeMetaType{javax.management.ObjectName}s (was: expose ObjectNames as
SimpleMetaType.STRINGs rather than
ImmutableCompositeMetaType{javax.management.ObjectName}s)
Description:
Properties representing ObjectNames in the Topic and Queue ManagedComponents are currently
exposed as a complicated CompositeValueSupport type that contains a String and a
Properties child value, e.g.:
name=serverPeer, viewUse=CONFIGURATION, mandatory=false, value= CompositeValueSupport:
metaType=[ImmutableCompositeMetaType{javax.management.ObjectName items
=[name=domain type=java.lang.String], [name=keyPropertyList type=java.util.Properties]}]
items=[domain=SimpleMetaType:java.lang.String:jboss.messaging,keyProper
tyList={service=ServerPeer}]
Items:
domain=SimpleMetaType:java.lang.String:jboss.messaging
keyPropertyList={service=ServerPeer}
I think exposing it as a simple value of type SimpleMetaType.STRING would make things
easier for Jopr/EmbJopr, as well as other clients of the management interface. As it's
exposed today, just to get it into a usable format, the client would have to write code to
convert the CompositeValue into an ObjectName, rather than being able to simply call new
ObjectName(simpleValue.getValue()).
was:
Properties representing ObjectNames in the Topic and Queue ManagedComponents are currently
exposed as a complicated CompositeValueSupport type that contains a String and a
Properties child value:
name=serverPeer, viewUse=CONFIGURATION, mandatory=false, value= CompositeValueSupport:
metaType=[ImmutableCompositeMetaType{javax.management.ObjectName items
=[name=domain type=java.lang.String], [name=keyPropertyList type=java.util.Properties]}]
items=[domain=SimpleMetaType:java.lang.String:jboss.messaging,keyProper
tyList={service=ServerPeer}]
Items:
domain=SimpleMetaType:java.lang.String:jboss.messaging
keyPropertyList={service=ServerPeer}
I think exposing it as a simple value of type SimpleMetaType.STRING would make things
easier for Jopr/EmbJopr, as well as other clients of the management interface. As it's
exposed today, just to get it into a usable format, the client would have to write code to
convert the CompositeValue into an ObjectName, rather than being able to simply call new
ObjectName(simpleValue.getValue()).
expose ManagedProperties representing ObjectNames as
SimpleMetaType.STRINGs rather than
ImmutableCompositeMetaType{javax.management.ObjectName}s
------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBAS-6688
URL:
https://jira.jboss.org/jira/browse/JBAS-6688
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: ProfileService
Reporter: Ian Springer
Assignee: Scott M Stark
Priority: Minor
Properties representing ObjectNames in the Topic and Queue ManagedComponents are
currently exposed as a complicated CompositeValueSupport type that contains a String and a
Properties child value, e.g.:
name=serverPeer, viewUse=CONFIGURATION, mandatory=false, value= CompositeValueSupport:
metaType=[ImmutableCompositeMetaType{javax.management.ObjectName items
=[name=domain type=java.lang.String], [name=keyPropertyList type=java.util.Properties]}]
items=[domain=SimpleMetaType:java.lang.String:jboss.messaging,keyProper
tyList={service=ServerPeer}]
Items:
domain=SimpleMetaType:java.lang.String:jboss.messaging
keyPropertyList={service=ServerPeer}
I think exposing it as a simple value of type SimpleMetaType.STRING would make things
easier for Jopr/EmbJopr, as well as other clients of the management interface. As it's
exposed today, just to get it into a usable format, the client would have to write code to
convert the CompositeValue into an ObjectName, rather than being able to simply call new
ObjectName(simpleValue.getValue()).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira