In this
interoperability vs. portability connection, the following quotation from Roger
Sessions (extracted from http://www.cips.ca/news/national/news.asp?aID=1698) may also be instructive:
<quote>
From my
work on CORBA, at IBM, I learned the difference between standards that succeed
and those that fail. I learned that standards that focus on portability fail
while those that focus on interoperability often succeed. CORBA was a huge
standards activity. It could be divided into two areas. The first was the hugely
complex CORBA API, which focused on portability. This easily accounted for 95%
of the CORBA activity. The second was IIOP, which was about interoperability. It
accounted for at most 5% of the CORBA activity. Although the CORBA API received
almost all of the early hype, it was ultimately the lowly IIOP that was the only
part of CORBA that had any real success.
</quote>
Worth reading from the same source: "What is a SOA?" (http://www.objectwatch.com/newsletters/issue_45.htm)
-----Original Message-----Portability and interoperability are different issues.
From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Anne Thomas Manes
Sent: mardi 18 avril 2006 14:05
To: [email protected]
Subject: Re: [service-orientated-architecture] WS-Portability or WS-Proprietary?
The WS framework is *not* designed to enable portability. When you implement a service using a particular SOAP toolkit, that service implementation is bound to that toolkit, and it can run only in containers supported by that toolkit.
The Java community, which always strives to support portability, has defined WS APIs (JAX-RPC and JAX-WS), which are supposed to enable portability across Java-based SOAP toolkits, although as Andrew points out, portability is not so easy. The APIs are the same across different toolkits, but the configuration and administration tools are not -- hence JAX-RPC/JAX-WS are about as portable as EJBs. But I repeat: portability is not a goal of the WS framework.
The WS framework *is* designed to enable interoperability. Services built using any WS-compliant toolkit can interoperate, regardless of the toolkit, language, container, or OS they are implemented with.
Based on my interviews with Fortune 500 companies, portability isn't especially important, but interoperability is.
btw -- I am not a WS-only proponent. Application requirements should always dictate technology choices. As a rule, I always recommend standard protocols over platform/product/language-specific protocols unless there is a compelling reason to use the proprietary protocol. (Hence my reservations about J/JS and MOM-based ESBs.) I also recommend simpler solutions over more complex solutions as long as they meet the requirements ( e.g., POX wins over WS in situations where security, reliability, etc, aren't required).
Anne
On 4/18/06, patrickdlogan < [EMAIL PROTECTED]> wrote:> So, am I as a coder expected to do all this work myself or can I
> have a tool to do it? I'd prefer an automated approach as per
> Sanjiva because I wouldn't want this sort of cruft leaking into my
> codebase.
Andrew Townley has made the point in this forum previously that there
are portability issue with SOAP toolkits. Here is his blog entry that
explains the issue in full detail...
http://atownley.org/2005/11/in-search-of-portable-interoperability/
Anyone who believes they will walk the line with SOAP and remain
somehow "vendor independent" or even language independent, is only
consider one factor in the equation.
Theses SOA things are very big costs and the differences between an
investment in Jini/Javaspaces or some other ESB-like thing are not as
clear-cut as I think the WS-Only proponents are making it out to be.
Developing in a SOAP system is as binding to a language and an API as
is developing in Jini/Javaspaces. Only seems *more* proprietary.
-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/
| 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.
