WildFly 9 jboss-service.xml Depends Element JMX Name Support

[jfisherdev]

I am currently migrating some applications with jboss-service.xml descriptors that use the <depends> element from JBoss AS 4.2.2 to WildFly 9.0.2.

Starting with jboss-service_7_0.xsd, it appears that a depends element whose content is the JMX name of an MBean that the MBean depends on is no longer valid.

For example:

<mbean code="AppMBean" name="domain:name=AppMBean>
     <depends>domain:name=AnotherMBean</depends>
</mbean>

Under the new schema, it appears that the only valid content is another MBean element, which is also supported in previous schema.

Even though this is not valid per the schema, it appears that it may still work.

I set up some MBeans with dependencies on other MBeans using the <depends> element with the JMX name as the content, and I noticed that the invocation order of the start() lifecycle methods appeared to be influenced by these <depends> elements in the jboss-service.xml descriptor. I am not sure if this means that the <depends> element with the JMX content is being considered as it was previously.

Can anyone confirm whether or not this is supported in WildFly 9.0.2 or any other JBoss AS 7+/WildFly release?

[kabirkhan]

It isn't something which we have tested extensively, but the intent is that it should work as previously.

So in your case, AnotherMBean should start before AppMBean

[jfisherdev]

While I have not tested this extensively either, this does appear to be working.

Thank you for your response.