> But pretty much any product released in the last two years supports
> basic interoperability via web services.
When they are used carefully. And then the results are not always
pretty, even to the extent of one vendor sending a Word document
explaining how the WSDL can be hand-edited so other toolkits can
consume it. I would not describe the current situation as a
rip-roaring success.
> One of Sanjiva's points is that the vendors need to develop better
> tooling, but experience to date has shown that if the tooling is too
> focused on language APIs, it reduces interoperability.
This is a curious statement because there are several vendors that
support these API's (Jini/Javaspaces, JMS, etc.) for multiple
languages (Java, dotnet, C/C++) with apparent interoperable success.
> One of the features of SOAP is that it supports clean separation of
> infrastructure and application functionality, so the application
> code doesn't really need to be concerned with issues like knitting
> together authentication/access models -- all that can be handled
> external to the application using policy enforcement points (i.e.,
> mediators).
And so the point that Jini/Javaspaces really should be compared to
ESB-like systems rather than "just SOAP" because these mediators are
proprietary (even those that are open source require a commitment to
that specific implementation). J/JS does a lot more than "just SOAP".
J/JS may be the *most* open ESB-like system since it does have a
well-defined API, integration with an arbitrary number of other
protocols, an open-source implementation, etc.
-Patrick
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/service-orientated-architecture/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
