The main reason for decoupling the refresh from the lifecycle is that you can make multiple changes before actually refreshing, preventing 'interesting' situations. You could think of the refresh as a 'clean up everything not in use at this very moment', which you don't want to do while you're in the middle of serious home improvement.
Angelo On Sat, May 15, 2010 at 11:58 PM, Richard S. Hall <he...@ungoverned.org>wrote: > Actually, if it weren't that way then you pretty are forced to refresh > every time you did an update because old clients would continue to be wired > to the old version, but new clients wouldn't be able to, so you'd always be > splitting the service space. > > With this "leak" you actually have more flexibility if you update a > provider with a simple bug fix. If it was importing / exporting its API then > a refresh is not necessary to keep everyone in the same service space. > However, if you always separate your API from the impl bundle, then you > would likely not be impacted by such issues. > > -> richard > > > "Ales Justin" <ales.jus...@gmail.com> wrote: > > >Wow, it gets even leak-ier. :-) > > > >So, I guess in standard server side it makes sense to do refresh when some > bundle goes away? > >As that's definitely not how we would like to and actually don't handle > things in our (JBoss) kernel. > >(that's by default, but we made it configurable -- kernel's OSGi facade > has OSGi spec's notion) > > > >Or how do other app servers handle this? > > > >-Ales > > > >On May 15, 2010, at 6:22 PM, Alan D. Cabrera wrote: > > > >> I'll add a finer point and state that B's exports will still be > available for others to wire to until all the bundles that are wired to B > are refreshed. > >> > >> > >> Regards, > >> Alan > >> > >> On May 14, 2010, at 2:25 AM, Rellermeyer Jan Simon wrote: > >> > >>> Right, the exported package foo.bar.b will remain stale despite B being > uninstalled. The wire gets dropped/changed only when you explicitly refresh > A through the package admin, which could result in A falling back to > installed when there is no other matching exporter for foo.bar.b around. > >>> > >>> Cheers, > >>> > >>> Jan. > >>> > >>> ------------------------------------------------------------ > >>> MSc Jan S. Rellermeyer > >>> Systems Group, Department of Computer Science, ETH Zurich > >>> CAB E 78, Universitaetstrasse 6, CH-8092 Zürich, Switzerland > >>> http://www.systems.ethz.ch > >>> ------------------------------------------------------------ > >>> > >>>> -----Original Message----- > >>>> From: osgi-dev-boun...@mail.osgi.org [mailto:osgi-dev- > >>>> boun...@mail.osgi.org] On Behalf Of Roman Roelofsen > >>>> Sent: Freitag, 14. Mai 2010 11:14 > >>>> To: OSGi Developer Mail List > >>>> Subject: Re: [osgi-dev] OSGi core wiring lifecycle question > >>>> > >>>> On Friday, May 14, 2010 10:51:54 am David Bosschaert wrote: > >>>>> Hi all, > >>>>> > >>>>> I have a bundle A that imports package foo.bar.b from bundle B so it > >>>>> gets wired to bundle B. When I uninstall bundle B what happens to > >>>> that > >>>>> wire? > >>>>> > >>>>> Thanks, > >>>>> > >>>>> David > >>>>> _______________________________________________ > >>>>> OSGi Developer Mail List > >>>>> osgi-dev@mail.osgi.org > >>>>> https://mail.osgi.org/mailman/listinfo/osgi-dev > >>>> > >>>> AFAIK, nothing will happen until you refresh (refresh package) bundle > >>>> A. > >>>> > >>>> Roman > >>>> _______________________________________________ > >>>> OSGi Developer Mail List > >>>> osgi-dev@mail.osgi.org > >>>> https://mail.osgi.org/mailman/listinfo/osgi-dev > >>> > >>> _______________________________________________ > >>> OSGi Developer Mail List > >>> osgi-dev@mail.osgi.org > >>> https://mail.osgi.org/mailman/listinfo/osgi-dev > >> > >> > >> _______________________________________________ > >> OSGi Developer Mail List > >> osgi-dev@mail.osgi.org > >> https://mail.osgi.org/mailman/listinfo/osgi-dev > > > > > >_______________________________________________ > >OSGi Developer Mail List > >osgi-dev@mail.osgi.org > >https://mail.osgi.org/mailman/listinfo/osgi-dev > > _______________________________________________ > OSGi Developer Mail List > osgi-dev@mail.osgi.org > https://mail.osgi.org/mailman/listinfo/osgi-dev >
_______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
