Fwd: Axis Deserialization Behavior

[Buddhike de Silva <bu...@geeksdiary.com>]

Hi All,

Please see the thread below. It looks like we've found cases where
Axis fails to deserialize a message returned from a WCF service if we
add an optional element to the type after the Axis code generated.
Could you please let us know which settings we could use to prevent
that from happening? Thanks.

Cheers,

-Buddhike

> Buddhike please ask on the user list in Axis .. IIRC some optional stuff is fine but it depends on what deser approach is used.
> Sanjiva.
>
> On Fri, Feb 25, 2011 at 3:54 AM, Buddhike de Silva <bu...@geeksdiary.com> wrote:
>>
>> Hi Sanjiva,
>>
>> Hope you are well. Could you please let me know if Axis serialization/deserialization would break if there are additional elements in the XML payload than what's in the generated class? We are doing some interop work with Axis and WCF and your feedback would help us a lot to make the right decision.
>>
>> Cheers,
>>
>> -Buddhike

---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
For additional commands, e-mail: java-user-help@axis.apache.org