[jboss-dev] ObjectName property order
Thomas Diesler
thomas.diesler at redhat.com
Thu Feb 1 03:45:59 EST 2007
ObjectName.toString()
should not be used for comparison nor as key in HashMaps.
I fixed this once in the EJB3 code base.
Use ObjectName.getCanonicalName()
-thomas
Carlo de Wolf wrote:
> After breaking my head for two days why dependencies aren't working
> anymore, Ales kindly pointed out to me that my properties are in the
> wrong order. It turns out this is a global problem.
>
> If I deploy this:
> <?xml version="1.0" encoding="UTF-8"?>
> <server>
> <mbean code="org.jboss.mq.server.jmx.Topic"
> name="jboss.mq.destination:service=Topic,name=myTestTopic">
> <attribute name="JNDIName">topic/myTestTopic</attribute>
> <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
> </mbean>
> </server>
>
> I get this in jmx-console:
> jboss.mq.destination
> * name=myTestTopic,service=Topic
>
> Note the reversal of the properties. I'm digging down into this, but
> maybe this will ring a bell to someone.
>
> Carlo
>
> _______________________________________________
> jboss-development mailing list
> jboss-development at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development
>
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
More information about the jboss-development
mailing list