Hi,
Sorry I reread my post... http://community.jboss.org/thread/174057 the title
is correct but the text in the message is wrong. Sorry for the confusion.
The issue I am experiencing now with the new prototype is that unbind is called
before bind (on JBOSS OSGi).
In a previous prototype on
Giuseppe,
Bear in mind that it's also important what the target service is doing. If
there is one target service and it goes away very briefly (e.g. for its bundle
to be updated) then the component binding to it will of course have to be
unbound first and then rebound later.
The dynamic
Hi,
Are you refering to Section 112.5.10, Bound Service Replacement ?
This just applies to unary (cardinality of 0..1 or 1..1) services.
Your case involves multiple cardinality (1..n) and so this replacement
does not apply. Here the services are bound and unbound as they come
and go.
Regards
Thanks,
Ok I understand, yes tried this too.
I created 2 services (A and B) both implementation of Dictionary (which is the
interface the DS service descriptor below is listening to).
I tried to replace bundle A (same version different version) but I still get
the bundle A stop (which I
Thank you,
Yes I guess I had not read very well.. This actually works ok.
I clearly remember though in my previous prototype equinox to call bind first
in a 0..n configuration. But I guess this might be implementation specific.
Wondering why this does not apply to x..n . Just out of curiosity..
