axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Green (JIRA)" <>
Subject [jira] Updated: (AXIS-1663) LocalSender does not deserialize response message
Date Tue, 23 Nov 2004 16:18:35 GMT
     [ ]

Steve Green updated AXIS-1663:

    Attachment: test.diff

It looks like the fix to LocalSender revealed a bug in TestOutParams.  Funny.. I thought it
was supposed to work the other way around :)

By not adding the parameters to the Call, getOutputParamByQName() will default to assuming
that output params are the same type as the return type, which in this case is false. 

> LocalSender does not deserialize response message
> -------------------------------------------------
>          Key: AXIS-1663
>          URL:
>      Project: Axis
>         Type: Bug
>   Components: Serialization/Deserialization
>     Versions: current (nightly)
>     Reporter: Steve Green
>  Attachments: test.diff
> When using the LocalSender, the response message is not passed through the deserializer
and as a result, trying to call getValueAsType on some MessageElements results in an exception
because there is no DeserializationContext associated with the element.  This is the piece
of in question.  Please note the comments, and the commented out line.
>     // copy back the response, and force its format to String in order to
>     // exercise the deserializers.
>     clientContext.setResponseMessage(serverContext.getResponseMessage());
>     //clientContext.getResponseMessage().getAsString();
> Replacing the commented line with this line solves the problem.
>     clientContext.getResponseMessage().getSOAPPartAsString();
> Was this functionality commented out for any particular reason?

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