When you add a new element to your type, how the
client is impacted really depends on how the
deserializer has been coded assuming it relies on Axis
serializers/deserialiers. (It is not really a java
issue : Note that stubs have already been generated)
Ideally bean deserializer should simply igno
Cory,
If you're using MESSAGE style services, then, yes, I would expect the
client to be able to handle the change -- no sweat. If you're using RPC,
WRAPPED, or DOCUMENT style, I would expect the deserializer to barf. Java's
not too good at handling the dynamic introduction of a new element in
All,
We've recently added a new member to an object being returned in our response payload.
Basically we've added a simple type to a complex type that clients are used to
consuming. We've appropriately updated our WSDL and I've updated our custom serializer
to return the new member. My questio
