[jboss-dev-forums] [JBoss OSGi Development] - Re: Unexpected dependee state changes
alesj
do-not-reply at jboss.com
Wed Dec 2 05:24:02 EST 2009
"thomas.diesler at jboss.com" wrote :
| I realize that this behaviour may not be natural to MC, but it is how OSGi works AFAIU.
|
| After uninstall of X, B should still be able to load classes from X. ServiceTracker should be used to act upon the unregistered services from X, but this would apply to bundleX.stop() as well.
|
Both of these seem very un-natural to me.
* class leakage?
* stale services usage
* ...
Is there a valid reason to allow this?
Does it say when the PackageAdmin::refresh needs to be invoked?
(btw: why is PA even mentioned wrt core framework? shouldn't core be "self-enough")
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4268462#4268462
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4268462
More information about the jboss-dev-forums
mailing list