soap encoding namespace for xsi:type fails when deserializing basic types
-------------------------------------------------------------------------
Key: AXISCPP-938
URL: http://issues.apache.org/jira/browse/AXISCPP-938
Project: Axis-C++
Type: Bug
Components: Server - Deserialization, Client - Deserialization
Versions: 1.5 Final, current (nightly)
Reporter: Adrian Dick
Assigned to: Adrian Dick
This problem has been reported on the mailing list: (
http://marc.theaimsgroup.com/?l=axis-c-user&m=113892568813046&w=2 )
I also recall this problem having been reported before.
The problem appears to be with the namespaces used in RPC/encoded messages.
Looking at the messages produced by the Axis c++ serializer, and the
corresponding deserializer logic, it would appear we only handle the XSD
namespaces:
http://www.w3.org/2001/XMLSchema
http://www.w3.org/1999/XMLSchema
but we should also support the soap encoding namespaces
http://www.w3.org/2001/06/soap-encoding
http://schemas.xmlsoap.org/soap/encoding/
Meaning a message containing this will work:
<stringType xsi:type="xsd:string" xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
The quick brown fox jumped over the lazy dog.
</stringType>
While the following will fail:
<stringType xsi:type="soapenc:string"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";>
The quick brown fox jumped over the lazy dog.
</stringType>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
