David Lindelöf wrote:
On Thu, 2007-07-05 at 15:15 -0400, Richard S. Hall wrote:
If you have a class with static methods that you want to share, just
create a bundle that exports the package containing that class. Client
bundles simply need to import that package and they can use the static
methods like they normally would.
Like a library bundle? I agree it's the easiest, but is there any way to
handle the lifecycle of such a class?
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.
-> richard
Is there a way to register a service object whose class has static
methods? (In such a way that those methods become available to other
bundles in the framework?)
--
--------------------------------------------------
David Lindelöf
Station 18
LESO-PB/EPFL
1015 Lausanne
tel +41-21-693.5556
mob +41-79-415.6641
fax +41-21-693.2722
e-mail [EMAIL PROTECTED]
url http://lesowww.epfl.ch/doctorants/lindelof/
weblog http://www.visnet.ch/smartbuildings/
--------------------------------------------------
Adler's Distinction:
Language is all that separates us from the lower animals,
and from the bureaucrats.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
