river-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michal Kleczek <michal.klec...@xpro.biz>
Subject Re: Jini and OSGI revisited
Date Sat, 09 Oct 2010 15:57:00 GMT
I've sent my message to early...

On Saturday 09 of October 2010 17:52:59 Michal Kleczek wrote:
> On Saturday 09 of October 2010 15:54:49 Sim IJskes - QCG wrote:
> > 
> > And downloading a jar? A jar has everything already. Dependencies,
> > codesigning. Extendable manifest, etc.
> 
> 
> 2. Dependencies - that is something I am not really sure is needed in OSGI
> - the service can provide everything that it needs in its bundle and
> express its public packages (a service interface) as exports.
> But it seems useful if we don't want to depend on OSGI container - service
> interface would be provided by a dependency. If the client depends on the
> same dependency Module (the problem of Module identity is something to be
> solved anyway - I would go for Java object identity here) there would be
> no ClassCastExceptions.
> In OSGI they don't do any harm - it is just that a service can provide some
> of its code in it's own bundle and some - as dependencies.

But a Jini service actually consists of two (or more) Modules - a server 
module and a proxy module. So deploying a service is actually installing two 
modules (server and its proxy module as a dependency). Objects sent over the 
wire would be annotaded only by a proxy module.

Michal

Mime
View raw message