Sanjiva Weerawarana wrote:
> Dan, I'm going to bow out of this debate. I don't think I'll ever
> convince you that there's anything different about WS-* vs. Jini and I'm
> pretty sure you won't convince me Jini does it all.
>
> IMO its not realistic to think that a technology "makes it", or not,
> purely based on its technical merits. Maybe Jini can indeed do it all,
> but that's irrelevant: does MSFT support it? What about IBM? What about
> Oracle? What about SAP? What about IONA? What about Macromedia? What
> about a host of other companies? (No, I won't say "What about
> WSO2?" ;-))
The point about Jini is that it can use any of the Java based toolkits that
provide interworking with these systems in the endpoint or invocation layer.
This lets a document service, and RPC service or anything else be interfaced to
a Jini service. I.e. Jini can talk web services or anything else.
I really hate to keep having to argue the point that Jini is a Java based
application framework. Thus, if Java can do WS-*, it follows that Jini based
services can too. Now, some types of tools are being wired into IDEs and into
app servers and into code generated by IDEs that will only run in a particular
type of container. It's those kinds of dependencies on an environment that
lock
you into a vendor and a language and most likely, a particular version/release.
There are a lot of common complaints and restrictions being argued on both
sides
of this WS-* vs Jini argument. As Patrick said, its really more about Jini as
an ESB or some other platform than it is about the WS-* standards.
What I and others it seems have against the "WS-* everywhere" mantra is that
there are enough issues with WS-* that it's hardly a "done deal." When all is
said and done, many Jini users will probably also be using WS-* as the means to
integrate with some things.
But Jini is more than just an integration technology. WS-* is all about
integration. It just so happens that over time, the WS-* crowd is finding out
that distributed integation has the same problems as distributed systems using
proprietary or otherwise binary protocols.
The 8 fallacies of distributed computing are applicable no matter what protocol
is on the wire.
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/
