Yes if your client is in the same VM it's the normal OSGI way
But if my client is in another VM than the service and the service is
lookup through InitialContext.lookup, is the Import-Package list used by
JNDI ?
Jeremy Hughes a écrit :
I was thinking of a different solution. It depends whether you want
your client to have visibility to both versions of the service at
runtime. If you only need one then you can specify a version range in
the Import-Package header of the client which covers only the version
of the service you want. The client bundle will only be wired to the
bundle that exports the version of the service you want, so the other
version of the service, although registered in the service registry,
won't be visible to your client. Under the covers, OSGi figures out
which services are with the 'class space' of your client and only
gives you ones that you can see.
HTH,
Jeremy
On 24 June 2010 13:16, Erik Gollot <[email protected]> wrote:
Hello,
first, thanks for your work in the OSGI world !
This is my first question about Aries.
So, when we publish a service, we can specify a version number, ok ?
So, now, if I've published 2 versions of the "same service", how a client
can specify the version he needs when a "IntialContext.lookup" is performed
? Do we need an OSGIfied JNDI ?
Thanks
