From: Michel D'H. <mic...@tr...> - 2004-05-28 10:54:49
|
Manuel Santillan Palencia wrote: >The thing is that if bundle B is in INSTALLED, RESOLVED OR STARTED >state, then there is no problem in bundle A accesing a class from bundle >B. However, if bundle A tries to access a class exported when bundle B >is STARTING, he won't be able to do it. > Is it really because it is in Starting state, or because of what is done in the start method? I mean, if you "sleep" for 1 minute in the start method of B, and you access a class from A as you do when B is in another state (installed, resolved or started), do you still have the problem? And the other way round? If you do what is in the start method when the bundle is started, are you still blocked? >Is this the correct way of acting? Or should bundle A be able to access bundle B classes at any time? > > I don't have time to look into the source of Oscar, but from what I can imagine, the class loader of B is exporting its packages as soon as it is installed. So we are back to pure Java, not OSGi, and the state of the bundle shall have no influence. Regards Michel |