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

[ https://jira.jboss.org/jira/browse/JBIDE-6161?page=com.atlassian.jira.plu... ] Brian Fitzpatrick commented on JBIDE-6161: ------------------------------------------ One suggestion that came up is to check to see if JBossWS is used as the runtime, have the WSDL URL field default to the internal:// name convention. According to the ESB Programmer's Reference (4.7), for the wsdl property of the SOAPProxy action: The original wsdl url whose WS endpoint will get re-written and exposed as new wsdl from the ESB. Depending upon the <definitions><service><port><soap:address location attribute's protocol (for example "http"), a protocol-specific SOAPProxyTransport implementation is used. The value can reference a location based on five different schemes: http, https, file, classpath or internal (JBossWS). Here are some examples: http://localhost:8080/Quickstart_webservice_proxy_basic_ws/HelloWorldWS?.... https://localhost:8443/webservice_proxy_security/HelloWorldWS?wsdl file:///tmp/HelloWorldWS.wsdl classpath://META-INF/HelloWorldWS.wsdl internal://jboss.ws:context=Quickstart_webservice_proxy_basic_ws,endpoint=HelloWorldWS So in the case of the myESB.esb file, we'd need to include the WSDL file path differently in the ESB config. For example, if we included it in the ESB archive itself in the META-INF folder, it would be: classpath://META-INF/MyWSDL.wsdl -- 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