This is an expected behavior if you don't do a refresh. Restarting a bundle does not change the wiring. After uninstalling the bundle, use the refresh command and you should see the behavior you expect.
On Tue, Sep 24, 2013 at 8:29 PM, Charles Moulliard <ch0...@gmail.com> wrote: > And Blueprint too .... as i have done a test and behavior is the same > Personally I would prefer that we improve that. Otherwise what will be > here the benefit to promote OSGI ? > > > > On Tue, Sep 24, 2013 at 6:44 PM, Johan Edstrom <seij...@gmail.com> wrote: > >> Spring dm replaces the classloaders for the bundles. >> >> Sent from my pressure cooker. >> >> On Sep 23, 2013, at 23:04, Charles Moulliard <ch0...@gmail.com> wrote: >> >> > Hi, >> > >> > Is there a reason why when we deploy 2 bundles where Bundle A = Spring >> DM >> > project = Spring XML File + Bean initialized using Class exposed by >> Bundle >> > B that when we remove Bundle B, the Bundle A (after osgi;restart) still >> > contain Class from Bundle B ? Does it work like that with Aries >> Blueprint ? >> > >> > Scenario >> > >> > 1) Package a bundle B containing a class com.mycompany.HelloWorld & >> > exporting this package >> > 2) Package a Spring XML file creating a bean (com.mycompany.HelloWorld) >> as >> > a Bundle A >> > 3) Deploy Bundle A, B >> > 4) Start them and verify in the log that by example init method of >> > HelloWorld has been called >> > 5) Stop Bundle B, remove it >> > 6) Restart Bundle A = Spring project. No error occurs ! >> > >> > Regards, >> > >> > -- >> > Charles Moulliard >> > Apache Committer / Architect @RedHat >> > Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com >> > > > > -- > Charles Moulliard > Apache Committer / Architect @RedHat > Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com > > -- ------------------------ Guillaume Nodet ------------------------ Red Hat, Open Source Integration Email: gno...@redhat.com Web: http://fusesource.com Blog: http://gnodet.blogspot.com/
