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

[Brian Fitzpatrick (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBIDE-6161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12525451#action_12525451 ] 

Brian Fitzpatrick commented on JBIDE-6161:
------------------------------------------

Ok, and here's some additional comments from David Ward about this issue to further muddy the water...

"But I must admit it was impossible for me to not peek at
the contents of myESB.esb when it was attached to the jira.  I won't dig
into this more, but something did jump out at me, regarding the hanging:

<action class="org.jboss.soa.esb.actions.soap.proxy.SOAPProxy"
name="myProxy">
     <property name="wsdl"
value="http://localhost:8080/myJSR181/order?wsdl"/>
</action>

This will not work.  Not any fault of SOAPProxy, mind you, as on a
restart Tomcat will simply NOT be listening yet.  The http:// wsdl uri
format was meant to be for wsdl that lives on other http servers.

There are multiple KNOWN workarounds for this.  The simplest is to
include the .wsdl file itself in the .esb archive, and use a
classpath:// wsdl uri, or you can drop it on the filesystem (not
preferred) and use a file:// wsdl uri.

However, the SUGGESTED mechanism when you're using JBossWS webservices
is to use the internal:// wsdl uri.  That, ALONG WITH the proper
deployment dependency on the barrier service MBean Tom Fennelly created,
should fix the hang problem.

For example, check out the samples/quickstarts/webservice_proxy_basic
quickstart...

jboss-esb.xml (the wsdl value starts with "internal://" plus the full
MBean name of the web service)
...
<action name="proxy" class="org.jboss.soa.esb.actions.soap.proxy.SOAPProxy">
     <property name="wsdl"
value="internal://jboss.ws:context=Quickstart_webservice_proxy_basic_ws,endpoint=HelloWorldWS"/>
</action>
...

wsbarrier-service.xml:
<?xml version="1.0" encoding="UTF-8"?>
<server>
     <mbean
code="org.jboss.internal.soa.esb.dependencies.WSDeploymentBarrierController"
name="jboss.esb:service=ProxyBasicHelloWorldWSBarrierController">
         <attribute
name="WsObjectName">jboss.ws:context=Quickstart_webservice_proxy_basic_ws,endpoint=HelloWorldWS</attribute>
     </mbean>
</server>

deployment.xml:
<jbossesb-deployment>
 
<depends>jboss.ws:context=Quickstart_webservice_proxy_basic_ws,endpoint=HelloWorldWS.Barrier</depends>
</jbossesb-deployment>

> 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