I actually posted a similar message to the group not too long ago --
> you can likely find it in an archive
Oops, and even with the same subject - sorry!
I certainly did a keyword search, but obviously not with
the "keywords" I then used for the subject..
Ah - one apology - you wrote "compatability" :)
So, we have the same opinion here, that changing this
behaviour of the Axis-generated stubs would be a good
thing.
Meanwhile I tried JWSDP, and it also fails
(deserialization error: unexpected element name:
expected=<old_field>, actual=<new_field>)
Both Axis and JWSDP seem to stick to the XML-schema
sequence definition in the WSDL very strictly..
(Actually, for JWSDP I had to change the sequences
to "all"-nodes in WSDL, see my post on Jun 20 2003)
Still the behaviour of other frameworks would be
interesting, as well as more general thoughts on
"web services and backwards compatibility".
Which certainly is, in large parts, nothing very
WS specific, but a general problem of distributed
computing.
--
Florian Lindauer
