Re: Jini vs/and OSGi
Adrian <[email protected]>
| Newsgroups | gmane.comp.java.sun.jini |
|---|---|
| Message-ID | <[email protected]> |
Dennis Reedy <dennis.reedy <at> gmail.com> writes: > > Hi Adrian, > > IMHO I see the two technologies as not opposed, but as working > together. OSGi as a micro-kernel architecture, Jini as technology > that makes Java services (components) accessible through the network. > OSGi does a really nice job at the JVM level (who knows whats going > to happen with JMS), Jini excels on the network (its primary domain). > > Enabling Jini technology based services to be activated as OSG > bundles may be the combination going forward. > > My very quick $0.02 > > Cheers > > Dennis > That's what I would've thought, but the action of removing Jini as a recommended spec to track/follow/integrate with, by the OSGi alliance seems to indicate otherwise. Recall that OSGi's initial focus was embedded devices (which could be networked) and being able to dynamically manage services on these. Sounds familiar... This, along with the imminent release (around May) of OSGi support from the Spring framework (http://www.springframework.org/osgi - one of the most popular and widely used open source server-side (primarily) do-all glue frameworks), points to a clear move, IMO, to bring OSGi to the enterprise space. What horse to bet on? 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]