[
https://jira.jboss.org/jira/browse/JBIDE-6161?page=com.atlassian.jira.plu...
]
Gary Lamperillo commented on JBIDE-6161:
----------------------------------------
Kevin and David,
Here is some more clarification on the issue:
1. quickstarts always deploy correctly and can start up during a fresh restart (run.sh),
because the projects include deployment.xml files, which wait for the dependencies on
restart.
2. When creating via JBDS, the user will not have the deployment.xml added, so the server
hangs on restart of the server. The myESB Project, in this case does not have a
deployment.xml. This leads to the tooling appearing as non-functional. This gives the
developer a poor experience. Yes, they can add the deployment.xml, but this should be the
value of using the tooling, it should be smart enough to take out the complexity of
dealing with these intricacies.
3. Here is what I'm proposing:
a. ESB Team provide a matrix that lists what items added to the esb.xml and the
associated items that should be added to the deployment.xml to the ESB Tooling Team
b. ESB Tooling Team modifies the ESB.xml tooling to dynamically adds/substracts
entries to the deployment.xml as it is being modified.
Here is a sample:
ESB.xml item | Dependencies
JMS Provider | jboss.esb.quickstart.destination:service=Queue,name=<Queue
Names>
SOAP Proxy | jboss.esb:deployment=soap.esb
Regards,
Gary
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.1
Attachments: hang_myESBXML.png
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