[
https://jira.jboss.org/jira/browse/JBIDE-6161?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBIDE-6161:
-------------------------------------
The JIRA is the wrong place to have any discussion about what *may* be the issue,
especially within the wrong project.
As mentioned in email, we already know the cause of the failure Aaron is seeing in SOA
4.3, a dependency on smooks was added into a core class without updating the location of
the jars.
This issue has already been fixed in trunk/SOA 5 but has since been superceded by the
performance work which removed the smooks dependency in that area.
As for the tooling changes, you should not have to modify the dependency.xml for esbs if
they are just relying on ESB functionality. You would only change this if depending on
external deployments (queues, your own deployments etc). We already specify an automatic
dependency on jbossesb.esb (for every deployment) and use the actionArtifactMap to derive
dependencies required by *our* actions. If there is an issue in this area then it is a
bug in the ESB, not tooling.
As for JBESB-2870, that issue is already in SOA 5.
If this is still an issue then can we please do as I had originally asked? Create an ESB
issue with the specific esb *deployment* and associated logs, then we can investigate
properly. If there is a bug in the ESB then it will be fixed.
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: 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