[esb-issues] [JBoss JIRA] Commented: (JBESB-2870) war/esb archive deployment dependencies/ordering not guaranteed

[Kevin Conner (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBESB-2870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12492543#action_12492543 ] 

Kevin Conner commented on JBESB-2870:
-------------------------------------

Could your barrier not query the currently deployed objects on startup?  It could then determine whether it has already been deployed and trigger the barrier, allowing the esb to only depend on the barrier and the war to deploy normally.


> war/esb archive deployment dependencies/ordering not guaranteed
> ---------------------------------------------------------------
>
>                 Key: JBESB-2870
>                 URL: https://jira.jboss.org/jira/browse/JBESB-2870
>             Project: JBoss ESB
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.6
>            Reporter: David Ward
>            Assignee: Tom Fennelly
>             Fix For: 4.7
>
>
> There should be a way to specify that an esb archive is dependent on a war archive to be deployed first before it is deployed.
> An example of this is a SOAPProxy action which points to a JBossWS webservice deployed in the same container.
> Right now, one can specify a deployment requirement of a war from an esb's deployment.xml file, but there are 2 problems with it:
> 1. You need to know the entire war deployment mbean object name, which unfortunately contains a generated id
> 2. The esb deployment will simply error instead of waiting for the dependent war to deploy.
> It is probable that we need to create our own barrier for this to work properly.
> We also need to test with wars contained inside esb archives, as well as exploded and zipped wars.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira