On Jul 10, 2007, at 15:53 , Richard S. Hall wrote:
David Lindelöf wrote:
If for instance the bundle is updated, will the client classes
"see" the
updated methods? I admit this is a bit beyond my understanding of
Java
classloading...
Yes, just a library bundle. Client bundles will not see new
versions of the library packages until the framework is refreshed.
So, you can control the life cycle by not doing a "refresh" until
you are ready. Refreshing the framework will not be transparent in
this case, since it will require stopping, then restarting all
client bundles, but there is no other way to deal with that.
Agreed, if you're sharing code between many bundles, they will all be
affected if that code changes. If that's unacceptable, the
alternative you have is to actually include a private copy of this
class in every bundle. That way you can control which bundles you
want to update when this class changes (but if you're fixing bugs in
such a class, you might end up updating all these bundles anyway).
Issues like this are very important when determining the actual
packaging of your code into bundles. Luckily, with OSGi, you have
many options and a lot of control over how you want things to happen.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
