ESB will not deploy if external web service is not available.

[robertusey]

I am using SOAPProxy action to pass the message to an external web service.  i.e.:

<action name="proxy_ws" class="org.jboss.soa.esb.actions.soap.proxy.SOAPProxy">

<property name="wsdl" value="http://externalhost:8080/external_webservice/ExternalWS?wsdl"/>

My issue is that the esb will not deploy if the web service is not available.  I get a "org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleException: Error configuring action processing pipeline" exception.

Is there any way to get around this because it would be possible in a production environment that has multiple web services in which one would not be available and not under our control.  I would still like to be able to deploy the esb.

[h.wolffenbuttel]

hi,

Is there a possibility to use the http router instead of the SOAPProxy? The http router has no need for services to be active.

Regards,

Hans

[robertusey]

That is useful information and will go that route if I have too but according to the programmers guide section for SOAAProxy, httprouter is not an appropriate or adequate mechanism:

page 130:

Other mechanisms of doing this are inappropriate or inadequate:

•

SOAPClient is used to invoke external web services, not mirror them.

•

SOAPProducer only executes internally-deployed JBoss WS services.

•

HttpRouter requires too much by-hand configuration for easy proxying.

Thanks

[tfennelly]

I think you can define the WSDL locally, in which case it will not attempt to read from the external webservice endpoint.  Check the docs.