|
Description:
|
hibernate-entitymanager's MANIFEST needs to identify a Bundle-Activator. This activator will be in charge of scanning for services/bundles and managing respective class loaders.
Attached is Martin & Steve's skeleton prototype which can be used as a starting point.
{quote}
The OsgiBundleClassLoaderServiceImpl is a Classloader which is only used internally - there will be one for each bundle. It could be also simply left out if the OsgiClassLoaderServiceImpl only manages the bundles and not "child classloaders". Like you already mentionend it was only a quick swab and I started with a classloader which wraps the functionality of osgi bundles. The OsgiClassLoaderServiceImpl is the interesting classloader which is the one which has to be registered with the bootstrap registry. There is always only one, and it encapsulates all the dynamic aspects of osgi (together with the listerners/activators) - because he knows all the bundles and is a single point of access/contol to osgi.
{quote}
{quote}
Other than these I think I see what you are doing here. The big questions I guess are (a) how the ClassLoaderService impl gets hooked in to BootstrapServiceRegistry and (b) what we actually look for in the bundles.
{quote}
{quote}
Thats one of the open questions, but from the osgi point of view it should happen in the start()-method of the bundle-activator if possible - or there could be a kind of deferred mechanism to register the classloader and begin scanning and registering services and bundles.
{quote}
|
