I had some simillar problems and finally decided to register the wsdl in my .esb file. This way the SOAPProxy always has the service definition (WSDL) available and is the startup sequence irrelevant. To difine the WSDL on the SOAPProxy you can do something like this:
<property name="wsdl" value="classpath:///sample/sample.wsdl"/>
<property name="endpointUrl" value="http://sampleserver:8080/sampleEndpoint"/>
So you need to point your property "wsdl" to your wsd-file location wich wil have to be on your classpath, unless you have a default location wich is named exactly the same (including drive path) with every installation.
thanks for your reply.
This can be a good solution, I will consider it.
By now I'm avoiding this problem ensuring that .ear modules will be deployed before the .esb modules (working on jboss deployment order)
I am facing the same problem.when i give the classpath in the value attribute,i m getting the configuration exception
unrecognized wsdl address:
Can you open a new topic and provide more information on your problem? That way you will get your answer sooner.