Stefan Tilkov wrote:
> WS-RM is a (or will be) an interoperability standard, JMS is an API.
> Relying on JMS makes your applications portable, relying on WS-RM
> will someday make them interoperable. To me, standardizing on
> protocols, not programming APIs, is a key feature of SOA.
JMS has an API which is equivalent in coupling to the use of WS-RM. Both have
specific semantic and technical features that your application should have an
abstraction layer to reduce the coupling.
I would caution against believing that one protocol is all you need. The
important issue is seemless invocation layer mapping to transport. This
provides the least impact to your application. The JERI stack in the Jini
toolkit, as I've said here before was designed with this specific issue in
mind.
If you are using Java, you can readily take advantage of this abstraction to
separate your application from the protocol.
Gregg Wonderly
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/
