[
https://issues.jboss.org/browse/AS7-6880?page=com.atlassian.jira.plugin.s...
]
Tomaz Cerar closed AS7-6880.
----------------------------
Fix Version/s: 8.0.0.Alpha1
Resolution: Duplicate Issue
This was fixed in AS7-6044
JBoss7 undeployment order
-------------------------
Key: AS7-6880
URL:
https://issues.jboss.org/browse/AS7-6880
Project: Application Server 7
Issue Type: Feature Request
Components: Server
Reporter: jboss_dev a
Assignee: Jason Greene
Labels: new_and_noteworthy
Fix For: 8.0.0.Alpha1
I have a jboss-all.xml which is placed in the META-INF folder of App1.war.
This descriptor defines a dependency on activemq.rar for 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
Would it be possible to have the undeployment order the reverse of what is given in
jboss-all.xml.That way App1.war will be undeployed first and then activemq.rar.I have
added a post for this in the forum as well.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira