[Users] Compatibility of Axis ( in BC-SOAP) with Spring-WS webservices

[Philip [via Petals Forums]]

Our PetalESB 4 sits in between webservices and webservices-clients written
with Spring-WS.
Apparently, Spring soes not set the SoapAction property , ans so Axis cannot
understand which method to invoke.
is there a Solution? 
See the interesting link about Axis2 : http://wso2.org/library/176 ( "How
Apache Axis2 Finds the Operation and Service a Message is Destined To ")

The 4 ways to detect the action are the following 
1/ HTTP request uri /axis2/services/EchoXMLService/echoOMElement 
2/ SOAPAction action="EchoOMElement" 
3/ QName of the first child of SOAP Body element <ns1:echoOMElement
xmlns:ns1="http://org.apache.axis2/xsd"> 
4/If WS-Addressing is enabled the address of To EPR (Endpoint Reference) and
Action element
<wsa:To>http://127.0.0.1:5556/axis2/services/EchoXMLService/echoOMElement</
wsa:To>
<wsa:Action>urn:EchoOMElement</wsa:Action> 

Using Petals ESB, the 1/ is not an option. The 4/ is eliminated because
users do not use ws-A. The 3/ is messy as the  first child of SOAP Body
element is a Request block, not the method name ..., so we need the 2/



_______________________________________________
If you reply to this email, your message will be added to the discussion below:
http://forum.petalslink.com/Compatibility-of-Axis-in-BC-SOAP-with-Spring-WS-webservices-tp4025258.html
To start a new topic under Users (get help, provide help), email ml-node+s974793n2681628h42 at n3.nabble.com
To unsubscribe from Users (get help, provide help), visit http://forum.petalslink.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=2681628&code=dXNlcnNAZm9ydW0ucGV0YWxzbGluay5vcmd8MjY4MTYyOHwtOTE3MDU0NjU4
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://forum-list.petalslink.org/pipermail/users/attachments/20120814/62daeab6/attachment.html>