axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adrian Dick (JIRA)" <>
Subject [jira] Updated: (AXISCPP-335) Client does not correctly deserialize complexTypes
Date Mon, 20 Dec 2004 15:56:13 GMT
     [ ]

Adrian Dick updated AXISCPP-335:


Patch to WSDL2Ws for initial problem.
This has been tested using Adrian's WSDL, with response and real server, but not for any other
RPC services.

> Client does not correctly deserialize complexTypes
> --------------------------------------------------
>          Key: AXISCPP-335
>          URL:
>      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

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
If you want more information on JIRA, or have a bug to report see:

View raw message