I have the following http:endpoints that consume and provide soap messages.
This definition works fine because I can view the wsdl and I can send and
receive soap. However when I try to use another SU in between like Saxon
and change the consumer's targetService to that of my Saxon SU I can't view
the wsdl anymore. Why is that so? I've also tried putting Camel in between
the two endpoints and the result is the same. It seems that any
targetService other than the http:endpoint provider causes it to fail. Are
these meant to be used exclusively?
<http:endpoint service="ns:PrimeNumbersConsumer"
endpoint="PrimeNumbersSoap"
role="consumer"
locationURI="http://localhost:8192/soap/prime/";
defaultMep="http://www.w3.org/2004/08/wsdl/in-out";
soap="true"
wsdlResource="classpath:consumer.wsdl"
targetService="ns:PrimeNumbers"
soapVersion="1.1"/>
<http:endpoint service="ns:PrimeNumbers"
endpoint="PrimeNumbersSoap"
role="provider"
locationURI="http://www50.brinkster.com/vbfacileinpt/np.asmx";
defaultMep="http://www.w3.org/2004/08/wsdl/in-out";
soap="true"
wsdlResource="classpath:provider.wsdl"
soapAction="http://microsoft.com/webservices/GetPrimeNumbers";
soapVersion="1.1"/>
I have tried using http:soap-consumer and provider instead and it works with
saxon in between but when I deploy that to SM in tomcat I get a weird
behavior where my locationURI gets rewritten fine but my wsdl isn't. The
only time I get the wsdl rewritten is when I use http:endpoint instead. See
my other posts about that problem which I haven't received a reply yet.
--
View this message in context:
http://www.nabble.com/Problem-viewing-the-WSDL-when-another-SU-is-in-between-soap-http%3Aendpoint-tp23980553p23980553.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
