Hi axis-developers, I've just deployed a simple Echo service using Axis1.2RC2 on Tomcat. I invoked the service using an Axis2 synchronous client and the log of request and response SOAP messages as seen on tcpmon are as follows.
Request: ------------- <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; xmlns:sample1="http://sample1.org/sample1";> <soapenv:Header> </soapenv:Header> <soapenv:Body> <sample1:echoString> <sample1:Text>Axis2 Echo String</sample1:Text> </sample1:echoString> </soapenv:Body> </soapenv:Envelope> Response: ---------------- <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> <soapenv:Body> <ns1:echoStringResponse soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"; xmlns:ns1="http://sample1.org/sample1";> <EchoStringReturn xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";>Axis2 Echo String</EchoStringReturn> </ns1:echoStringResponse> </soapenv:Body> </soapenv:Envelope> If you see the response message generated by Axis1.2RC2 <EchoStringResponse> appears to be a non qualified element. Whereas as a norm every SOAP Element is supposed to be qualified against a namespace (am I wrong?). I've not noticed it to be a serious problem, untill the OM implementation in Axis2 reported the error that it will not allow to (de)serialize SOAP message having non qualified elements in response message. Can this be fixed, with say giving a prefix to every non-qualified element same as that of the parent element. Should there be a need to log a jira issue, let me know. Thank you Jayachandra -- -- Jaya
