Ernie Varitimos wrote:
> The problem with RMI and Jini was at first marketing, Sun blew it. If
> it had been accompanied with a better story from the beginning,
> perhaps applications servers would have been Jini-based.
Sun's marketing team would not listen to the "don't use that line" arguments
from the Jini team, or so I've heard. They wanted to take the "devices" route
because J2ME was hot and so were a lot of other devices. The failed to deliver
any useful message...
> As a stand-alone technology it suffers because of complexity of setup
> and configuration. Requiring a registry and lookup service that you
> must have running to make remoting work is more weight than most are
> willing to deal with. We already have well established IP standards
> that provide these services (DNS, DHCP). An ancillary problem is
> exception handling. It's simply not robust enough.
The primary issue is that the Jini lookup server supports and exploits mobile
code. The DNS and DHCP standards can send some data, but they don't also share
all of the authentication and authorization capabilities that are now in Jini
via the JERI stack. If you have a service somewhere, having a Jini lookup
server with it is not that big of a deal. In earlier Jini versions, there was
not any type of container available, and so you had to run separate VMs for
each
Jini service. Now, the starter kit comes with the very useful
com.sun.jini.start package which a lot of people use. To put your service into
the container with the other starter kit services, you just need to have a
constructor like
public MyService( String args[], com.sun.jini.start.LifeCycle life );
There's some simple configuration needed as well to provide your codebase,
classpath, policy etc. But, that's not a big deal. If you haven't looked at
Jini in a while, you might want to. There are several tools to make things
easier, including the incax ide. Look at http://v2getsmart.jini.org (courtesy
of Dan Creswell) and there is lots more information there about how to make use
of the v2.x features.
> We need a remoting library that runs over IP networks that requires
> zero configuration, zero setup, like Bonjour. If Bonjour or a Bonjour-
> like technology were built into the JVM, RMI would be unnecessary,
> and remoting would be cleaner and easier. Although, this does not
> address exception handling.
What features of Bonjour do you think simplify things for remoting?
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/
