> Jini suffers... in order to play you needed their software on every
> box... getting it on every box is not easy.
>
> That's the big difference between CORBA, RMI, Jini, E-Speak and
> WS-*/REST. In Web services and REST style services, you don't need
> to go and download some software to participate .. all you need is
> an HTTP server and some code to process the standard messages coming
> on the wire.
This is an apples and oranges comparison. Yes, putting a SOAP port is
can be done using an IDE in just four steps. But Jini is more like an
"enterprise service bus". Simple SOAP can be integrated with either
and EBS or Jini.
Both the ESB and Jini require something to be installed on at least
one computer. Not necessarily the same server(s) as your simple SOAP
clients or servers, though.
The "Jini requires Java" doesn't fly so well either. An ESB-sized
infrastructure will require a significant new investment if one is not
already invested. The target audience is almost certainly invested in
Java to a reasonable degree. Those that aren't, say a pure Microsoft
world, are less likely to invest in any of the ESB-like
infrastructures.
I chalk up the slow start to EJB getting so much (undeserved)
attention for so many years, and to the failure of DCOM giving rise to
SOAP and its subsequent (undeserved) bandwagon.
Notice how there are really two architectures that get discussed on
this SOA forum: REST/HTTP and Jini/Javaspaces. No one talks about
"SOAP architectures" because a generic interface technology is not in
itself an "architecture".
-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/
