JBoss7 undeployment order

[nimmi]

Hello All,

I have used the descriptor file META-INF\jboss-all.xml to define deployment order.We have a App1.war which depends on activemq.rar as connection factories and queues are defined in the rar.

So I included a META-INF\jboss-all.xml with the below content in App1.war -

<jboss umlns="urn:jboss:1.0">

  <jboss-deployment-dependencies xmlns="urn:jboss:deployment-dependencies:1.0">

  <dependency name="activemq.rar" />

  </jboss-deployment-dependencies>

</jboss>

While starting the server the deployment order is correct.activemq.rar gets deployed first and then App1.war.

But when the server is stopped I see the queues and factories being unbound before App1.war is undeployed.This causes errors for App1.war

I was expecting App1.war to be undeployed first and then activemq.rar.

Could anybody please let me know if there is anything more to be done to achieve this.I did not find much on undeployment order.

jboss_dev

[nickarls]

You could file a feature JIRA and request that the undeployment order would be the reverse of the jboss-all.xml (if present). Worst thing that can happen is that it gets rejected.

[jaikiran]

How does App1.war depend on the queues and factories? Does it inject them somehow?

[nimmi]

Thank you for getting back to me.App1.war injects the queues and connection factories using Spring.

I followed the documentation given in the forum for successful integration of ActiveMQ with JBoss7.

Th pdf in this link - https://community.jboss.org/wiki/JBoss6EAPOr7xxToApacheActiveMQ56Or7 was very useful

I have created a feature JIRA https://issues.jboss.org/browse/AS7-6880 as suggested by Nicklas.