You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by "Adrian Dick (JIRA)" <ax...@ws.apache.org> on 2004/12/20 16:45:19 UTC
[jira] Updated: (AXISCPP-335) Client does not correctly deserialize complexTypes
[ http://nagoya.apache.org/jira/browse/AXISCPP-335?page=history ]
Adrian Dick updated AXISCPP-335:
--------------------------------
Attachment: WS021A.cpp
WS021A.wsdl
response.msg
WSDL, Client and server response, as provided by Adrian Smith, in initial report to mailing list.
> Client does not correctly deserialize complexTypes
> --------------------------------------------------
>
> Key: AXISCPP-335
> URL: http://nagoya.apache.org/jira/browse/AXISCPP-335
> Project: Axis-C++
> Type: Bug
> Components: Serialization/Deserialization, WSDL processing
> Versions: current (nightly), 1.4 Final
> Environment: RPC/Encoded
> Reporter: Adrian Dick
> Attachments: WS021A.cpp, WS021A.wsdl, response.msg
>
> Adrian Smith is seeing the following problems:
> 1) When running the client, the following error occurs:
> Warning - The configuration file was not found (/axiscpp.conf).
> Exception : Cannot deserialize the requested element
> Exception : 68
> After some investigation, the exception is being caused by a mismatch in the SOAP message and what the client stubs are expecting (as produced by WSDL2Ws).
> WSDL2Ws should be using the complexType name, rather than message name.
> 2) Having provided a resolution to 1) the following is seen:
> Warning - The configuration file was not found (/axiscpp.conf).
> returned
> result->telNr is NULL
> Suggesting the response is not being correctly deserialized, nor throwing any kind of exception.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira