Gregg Wonderly writes:
"I personally have no problem spending a day to create an neutralization
layer for a particular vendor, or legacy system so that I don't have to
compromise standards, integrity or flexibility of my SOA."
And later writes:
"Proprietary is an interesting term to through into the mix. The
specifications for Java and Jini are publicly available. You can license
Java technologies for your own implementation. If not, then you can
freely use the existing implementations, buy support packages and
otherwise have exactly the same scenario that you'd have with most other
commercially supported software environments that might be part of your
SOA. Jini is now open source. It's interface to the world is the JERI
stack."
One might be surprised to see the breadth of the open Jini platform
compared to the WS-* platform. A very thin layer of interoperability and
portability exists in the WS-* world in early 2006. Amazing. Not much
depth is available before a feature set becomes very vendor-specific.
I ran a short experiment with some folks recently testing
interoperability among various WS-* toolkits. What a pain. Very little
time was available for actual business value. Then we replaced those
WS-* toolkits with simple HTTP clients and servers. After a relatively
short amount of time learning the specific APIs we were very soon
spending nearly all of our time on business value. We paused
periodically to examine what we'd lost by moving from WS-* to pure HTTP.
We've yet to identify one thing of importance to us.
I'd like to see what others think we've lost.
The pieces I think we ultimately will find lacking though, *are* found
in Jini, no WS-* at least for the foreseeable future.
I'd like to see a non-Jini ESB vendor line their story up against Jini
to see what's added or missing, and whether those pieces are proprietary
or open.
-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/
