This probably needs to be fixed in the ServiceControllerContext in AS
code? We can do a simple wrapper around ObjectName name representation,
where equality is not dependent on the properties order. I can look at
that, np. ------------------- >> The order of properties in a depends
string should not matter. There are getCanonicalKeyPropertyListString()
and getCanonicalName() ObjectName methods that return the props in a
sorted order, but should not be needed for depends. Must be a change in
the depends lookup that is going to a string form which is not the
canonical format. 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