When the SOAPProxy action is constructed, it pulls the wsdl url as configured. The normal use case for a webservice proxy is that the webservice is "someplace else" and already available, and if it's not available, it rears itself as an initialization exception of the SOAPProxy. However, what if the webservice is deployed in the same server as the esbservice containing the SOAPProxy? Well, right now, the war containing the webservice needs to be deployed first before the SOAPProxy, and the HTTP connector has to be started and available. I'm starting this thread because I would like input on the following options (add more if you like): 1. Change nothing. Aren't proxied webservices normally external and should already be available? 2. *Lazily* initialize SOAPProxy on it's first real usage/invocation. I don't like this one because it's really a lie then if the esbservice seemingly successfully deploys, when in reality there's something wrong (in the case where the wsdl URL is bad or not available). 3 .Investigate using deployment.xml (<jbossesb-deployment>web applicationweb container</jbossesb-deployment>)? If this would work, I think it would be the best option. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4254498#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...