SOAP & tight coupling

[Nicolas Gouteux <go...@jpmorgan.com>]

SOAP promotes loose coupling between applications.
However, the standard BeanSerializer does not seem to like missing or extraneous
fields in structures.
It seems like if we have the same tight coupling constraints as CORBA and RMI!
Would not it be great if some kind of versioning were built into SOAP whereby a
server with minor changes
could still serve clients with an older version, and major changes would imply
the redeployement of new clients.
How can one achieve this? Should I plug in my own 'Weak-Serializer'?
If anyone has ideas!...

regards
Ngx



This communication is for informational purposes only.  It is not intended as
an offer or solicitation for the purchase or sale of any financial instrument
or as an official confirmation of any transaction. All market prices, data
and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of J.P. Morgan & Co. Incorporated, its
subsidiaries and affiliates.