|Multiple versions of bundle [message #105375]
||Tue, 19 February 2008 13:05
| Jeff Lowcock
Registered: July 2009
I have created three bundles A_1.0.0, B_1.0.0 and B_1.0.1|
A listens via a ServiceTracker for service updates. When a new service is
added A lauches a thread which uses the new B_1.0.0 service for a number
of iterations and then exits. B_1.0.1 is installed and resolved but not
started. B_1.0.1 is started only once the B.1.0.0 service has completed
its' execution loop so it seems that B_1.0.0 or A_1.0.0 holds onto the
service until completion and then the release of the service allows
B_1.0.0 to be stopped and B_1.0.1 to be started which then is detected via
the service tracker and all proceeds per the code.
However this is not the behaviour that I expected I was expecting the
newer version of the bundle to begin immediately and not have to wait
until after the initial version had completed.
The scenario is a number sessions in a server will be concurrently active
and I want to cause new sessions to use the newest version of the bundle
to acquire new functionality. I had understood the I could run more than
one version of the bundle at the same time with older sessions using the
original version and newer sessions using the new version.
Do I understand correctly and if so is there some configuration that I
need to look at to support this requirement.
Powered by FUDForum
. Page generated in 0.05842 seconds