Re: [oscar-devel] DriverLocator (part 2)

[Richard S. H. <he...@un...>]

Marcel Offermans wrote:

>The exact same setup and bundles work in JES 2.0: my driver gets called
>there. This is strange since bundles should not be dependent on a
>specific server framework so JES's device.jar bundle should work. On a
>related note, I found out something else.
>

Well, it does sound like it could be an issue with Oscar then.  If you 
want you can send me (privately) the driver with instructions on how to 
repeat the situation and I can look into it on both JES and Oscar.

>The specs state: "Exported packages from a bundle are available to other
>bundles as soon as that bundle completes installation on the framework".
>That state (as far as I understand) is the INSTALLED state.
>

Yeah, I wrestled with the meaning of this too...you obviously know how I 
interpretted it.  :^)

>Installing both bundles on Oscar and starting the device.jar works. If
>you do the same on JES 2.0 it complains about the import. Starting and
>stopping the log there leaves that bundle in the RESOLVED state. If you
>then start device.jar, it works.
>

I like my way better.  ;^)  But seriously, though, this looks like it 
might have changed in OSGi 2.0, which states on page 26, "If the 
bundle's dependencies are resolved, all the packages declared in the 
bundle's Export-Package manifest header are exported to the OSGi 
environment."

This appears to be a change, perhaps.  I have gone through the framework 
portion of 2.0 and highlighted every place where it sounded like they 
refined the definition of some functionality.  I expect to slowly 
incorporate these refinements in future releases of Oscar.

>I'm not sure if this has anything to do with the device manager not
>working in Oscar though...
>

I wouldn't think so, but you never know.

-> richard