[
https://jira.jboss.org/jira/browse/JBIDE-6161?page=com.atlassian.jira.plu...
]
Gary Lamperillo commented on JBIDE-6161:
----------------------------------------
Brian and David - Thanks for the information
A couple of comments:
1. attached is another screenshot that shows that the tooling does not allow a browse the
project to add a wsdl from the META-INF.
2.using path just described: classpath://META-INF/MyWSDL.wsdl returns a null pointer.
3. It would be more intuitive to use the wsdl path as described previously:
http://localhost:8080/myJSR181/order?wsdl
and cache this on start up.
4. The standard mode of operation for an esb should be that nothing should hang it.
Hanging for 1 service, will effect other services that must be up and running. How will
an Operational team debug this? A better approach would be to bring it up and let the
team debug the services should there be issues. Why must the wsdl be dynamically read?
11Why can't it be cached based on the wsdl given?
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, Screenshot-Add SOAP Proxy .png, 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