-
Sub-task
-
Resolution: Done
-
Blocker
-
None
-
None
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=
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()).
- is related to
-
JBAS-6711 if non-null values are set for ObjectName ManagedProperties (i.e. DLQ, serverPeer, or expiryQueue props) in Topic/Queue templates, applyTemplate() throws "IllegalArgumentException: Not handled value: CompositeValueSupport"
- Closed