B could be STARTING because of lazy activation. In that case, it can be quickly stopped for the refresh.
But, as Richard notes, it is the wiring that is important. If B is wired to A and A is refreshed, then B must be refreshed. Since B is being refreshed, the framework will need to stop it if it is not in the RESOLVED state and then restart after refresh. -- BJ Hargrave Senior Technical Staff Member, IBM OSGi Fellow and CTO of the OSGi Alliance [email protected] office: +1 386 848 1781 mobile: +1 386 848 3788 From: "Richard S. Hall" <[email protected]> To: OSGi Developer Mail List <[email protected]> Date: 2011/05/06 10:09 Subject: Re: [osgi-dev] Q on PackageAdmin#refreshPackages() Sent by: [email protected] On 5/5/11 21:41, Ikuo Yamasaki wrote: > Hi OSGi Experts, > > I have a question(confirmation) on Package Admin Service Spec in R4.2 > Core Spec. > > ============================================== > [Precondition] > Bundle-A exports package p (version 1.0). > Bundle-B imports package p (version 1.0). > > [Then] > 1. Bundle-A is updated: exports package p (version 1.1). > 2. PackageAdmin#refreshPackages(new Bundle[]{Bundle-A})is called, while > Bundle-B is in the state of STARTING. > > [Expected behaivior] > Bundle-B will continue to import package p (version 1.0), > because section 7.5.3.11 does not mention about STARTING/STOPPING at all. > ============================================== > > Is my understanding correct ? No, I don't think so. If bundle B is wired to A, it will be pulled into the refresh operation. Either the refresh operation will end up waiting for B to become active before stopping it and refreshing it or the entire refresh operation will fail because B couldn't be stopped. -> richard > Best regards, > > --------------------- > NTT Cyber Solutions Laboratories > > Ikuo YAMASAKI > E-mail: [email protected] > TEL +81-46-859-8537 FAX +81-46-855-1282 > > > _______________________________________________ > OSGi Developer Mail List > [email protected] > https://mail.osgi.org/mailman/listinfo/osgi-dev _______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
