reetings,
I am struggling with something. I am trying to use the JMS URL-based
transport implementation in Axis. It works great!! -- except for one
glitch.
If I use a rpc/encoded WSDL -- where the namespace of the wsdlsoap:body
element is equal to the targetService (namespace="Pinger" as shown below) --
the targetService is determined correctly, without my intervention in the
JMSListener...
i.e.
<wsdl:binding name="PingerSoapBinding" type="impl:Pinger">
<wsdlsoap:binding
style="rpc"transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="ping">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="pingRequest">
<wsdlsoap:body
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"; namespace="Pinger"
use="encoded"/>
</wsdl:input>
But if I use doc/literal -- the targetService cannot be determined without
my intervention (i.e. "targetService is null" -- and I must call
setTargetService() on the messageContext in the JMSListener. The wsdl
snippet is below...
i.e
<binding name="Example_GetListSoapBinding" type="svc:Example_GetList" >
<soap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http"; />
<operation name="SubmitExample_GetList" >
<soap:operation soapAction="svc:SubmitExample_GetList" />
<input>
<soap:body use="literal"
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"; /> -->
</input>
Note: that if I use "namespace=Example_GetList", it doesn't help...
Should this work?? Has anyone gotten this to work?? If so, can anyone send
me a code snippet??
Do I have to hack the JMSSender & JMSListener to pass this info in the JMS
Message headers -- or else somehow in the SOAP Headers -- or perhaps in the
URL ?? What is the magic setup??
It would be fantastic if I could make this work out-of-the-box with Axis.
Otherwise the client has to do something special when using JMS over HTTP,
when with the current setup it is transparent in the URL lookup...
Thanks very much,
-- Chris
