On 7/10/06, Sanjiva Weerawarana <[EMAIL PROTECTED]> wrote:
>Despite all the discussion about alternatives such as HTTP/Jini/CORBA,
>I'm still convinced that WS-* is the best technology *available today*
>to implement SOAs that do real "enterprisey" stuff.
One point to pick out here. Jini is a Java programming language based
technology that includes the abilility to use HTTP, CORBA, MODBUS,
strings-and-cans, semaphore flags, and just about any other wire protocol for
transporting the appropriate invocation layer technology (JRMP, JERI, WS-*,
Smoke-and-mirrors etc). Putting it in comparison with HTTP and CORBA is really
out of place. You should use HTTP/JRMP/JERI/CORBA together to indicate an
invocation layer/messaging/transfer mechanism comparison.
...following this track, and only slightly related...
My repeated reponses to Anne's and others statements about Jini not being
appropriate for SOA because it is too Java focused has included attempts to
argue the points of clean separation between programming and remote
invocation/messaging implementations. People refering to Jini as another RPC
technology is a shortsighted viewpoint from this perspective.
Jini is a distributed systems programming platform that exploits the Java
platfor to provide Service Oriented design. It includes the ability to plug in
an invocation layer suitable for talking to WS systems, RESTful systems and
many
others.
So, I still fail to really understand why there is so much
no-not-jini-its-too-java-restricted when really, any solution for WS-*, REST or
some other invocation/messaging/transfer layer/mechanism is also bound to a
particular programming platform/language.
What Jini/Java brings to the table is the choice of mobile code to be used to
simplify versioning and client updates. It provides a set of standardized
(through specification) APIs which facilitate dealing with all of the 8
fallacies of distributed computing, out-of-the-box.
The only code you have to write is your application, and perhaps a custom
endpoint or invocation layer factory for a specific system interface. This
might include a layer of mediation to manage system interactions. But, because
Jini has a standard place to plug such things in with a standard API, reuse is
greatly facilitated.
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/
