[oscar-devel] DriverLocator (part 2)

[Marcel O. <mar...@es...>]

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.

The device.jar needs log.jar; it imports a package that log.jar exports
(I know there can be other "providers" of this package, but let's assume
that these are the only two bundles we use).

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.

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'm not sure if this has anything to do with the device manager not
working in Oscar though...