[esb-issues] [JBoss JIRA] Closed: (JBESB-1359) Wrong deployment order of nested archives
[ http://jira.jboss.com/jira/browse/JBESB-1359?page=all ]
Kevin Conner closed JBESB-1359.
-------------------------------
Resolution: Done
I have modified the deployer to support <esb-depends> tags within deployment.xml.
This tag takes the name of the war file, which must be an immediate sub deployment of the
esb artifact, and creates a dependency on it.
e.g. <esb-depends>Performance6.war</esb-depends>
Included in revision 16938.
Wrong deployment order of nested archives
-----------------------------------------
Key: JBESB-1359
URL: http://jira.jboss.com/jira/browse/JBESB-1359
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.2.1
Reporter: Martin Vecera
Assigned To: Kevin Conner
Fix For: 4.2.1 CP1
When I have an .esb archive that contains one ESB service and one .war archive. The
service uses SOAPProcessor to send messages to the web service inside the nested .war. I
have deployed a queue with some messages. Whenever I try to deploy my .esb archive the web
service is deployed later than the ESB service. Then the ESB service starts processing the
message and the SOAPProcessor fails because the web service is not deployed yet.
I think the correct deployer behaviour would be:
1) if there are any nested archives then call the deployer for each of the nested
archives
2) deploy the services from the current archive
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira