[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-6161) ESB Projects stall on start

[Max Rydahl Andersen (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBIDE-6161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Max Rydahl Andersen updated JBIDE-6161:
---------------------------------------

    Fix Version/s: 3.1.x
                   3.2.next
                       (was: 3.1.1)


btw. I completely agree that we should not be automatically adjusting deployment.xml as the first thing.

1) the runtime (esb) should be able to reduce maybe even elliminate the need for it

2) if we are able to actually figure out safely what should be added to dependency.xml then it should be done by validations/quickfixes not automagically edits to such a brittle file as deployment.xml

and finally, most definitely not for 3.1.1 since it is only in specific cases (usage of smooks) which we currently can't easily detect.

> ESB Projects stall on start
> ---------------------------
>
>                 Key: JBIDE-6161
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-6161
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: esb
>    Affects Versions: 3.1.0.GA
>            Reporter: Gary Lamperillo
>            Assignee: Brian Fitzpatrick
>             Fix For: 3.1.x, 3.2.next
>
>         Attachments: boot.log, deployment.xml, hang_myESBXML.png, JbrEsb.esb, myESB.esb, myJSR181.war, server.log
>
>
> When developing an Application ESB, the ESB archive works fine when it is deployed last, but on server restarts the archive hangs.  It appears there are dependencies not being met for Application ESB.  When a ESB Project is created a deployment.xml should be added to the META-INF which adds all the dependencies.

-- 
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