internet somewhere) of WSDL changes that break existing consumers,
and has been verified via testing? I'm looking for a table that
would contain a list of changes, and then the behavior of various
SOAP stacks. For example, I know that adding an operation to a web
service has no impact on an existing WebLogic consumer of that Web
Service. I also know that adding attributes to a response message
doesn't impact .NET clients that aren't interested in that attribute,
as long as the structure of the rest of the message remains consistent.
I am looking for things that have actually been tested, versus
hypothetical behavior. One can presume that adding an operation
should not require a rebuild of existing clients except in the case
where those clients need the new operation. That being said, the
client side proxies are built using ant tasks, wizards, etc., and
what goes on inside of that generated code is unknown.
-tb
SPONSORED LINKS
| Computer software | Computer aided design software | Computer job |
| Soa | Service-oriented architecture |
YAHOO! GROUPS LINKS
- Visit your group "service-orientated-architecture" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
