Hi Alan, I agree, there is no reason a bundle should move to the INSTALLED (unresolved) state as a result of calling resolveBundles(). I opened bug https://www.osgi.org/members/bugzilla/show_bug.cgi?id=710 against the spec to remove this from the specification.
Tom
From: Alan Cabrera <[EMAIL PROTECTED]>
To: OSGi Mail List Developer <[email protected]>
Date: 06/01/2008 11:26 PM
Subject: [osgi-dev] resolveBundles() causing a bundle to become unresolved
Section 3.14.2 says "A Fragment bundle can become unresolved by
calling the refreshPackages method or the resolveBundle method on
itself or on its host." For the life of me, I don't understand why
resolveBundles() would force a fragment to become unresolved. What
did I miss?
Regards,
Alan
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
<<inline: graycol.gif>>
<<inline: ecblank.gif>>
_______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
