Jini vs/and OSGi

Adrian <[email protected]>
Newsgroups gmane.comp.java.sun.jini
Message-ID <[email protected]>
Hello,

Would anyone care to comment on where they see things heading with the
aforementioned specifications? There seems to be significant functional overlap
in current implementations. My impression is that OSGi is gaining a lot of steam
(mostly due to the huge success of the Eclipse project, I suppose) and will
probably be evolving to offer more and more of what Jini does. While
Jini/Javaspaces has also been in the news recently, OSGi seems to be leading in
developer/tool maker mindshare and there is a lot of 'real' work done in terms
of advancing the spec. This article, written at the end of 2005,
http://www.osgi.org/blog/2005/11/why-did-we-let-jini-out-of-osgi-r4.html doesn't
doesn't make it sound very promising for Jini (viewed through the subjective
eyes of the OSGi Alliance at least). I'm curious why there was no one (I'm
thinking GigaSpaces or Dan C., for example) to beat the drums for Jini to be at
least kept in the "Recommended" section of the OSGi spec.

Would it make sense to think of a JavaSpace as an OSGi service instead of a Jini
one when and if OSGi evolves to provide service lookup across a grid? Are the
security/classloader issues mentioned in the article areas that Jini will
address in the near term?

The following presentation talks about using OSGi and Jini together, so not
everyone seems to agree on where the future is headed for both specs.
http://www.jini.org/wiki/10th_JCM_Sessions#Service_oriented_components_on_the_grid_using_OSGi_and_Jini


Enquiring minds want to know.

Cheers,
Adrian

--------------------------------------------------------------------------
Getting Started:     http://www.jini.org/wiki/Category:Getting_Started
Community Web Site:  http://jini.org
jini-users Archive:  http://archives.java.sun.com/archives/jini-users.html
Unsubscribing:       email "signoff JINI-USERS"  to [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.