I'm starting to work with the activator and class loaders. Here's several questions that have come up, so far. Any input is appreciated!

1.) Should this really be revolving around hibernate-entitymanager? Theoretically, a user should be able to start only the hibernate-core bundle, programmatically create a Configuration, and use pure Hibernate. The environment could have the SessionFactory in one bundle with all Entities in another bundle. Therefore, should we put everything in core instead? Or, split up duties (ex: entitymanager scans for persistence contexts while core scans for almost everything else)?

2.) What else should the activator be watching for, other than Service?

3.) Dynamic bundles, coming and going during runtime, has been mentioned several times. But, for real-world applications, is it something we need to really worry about? Every OSGi project I've been a part of in the past had some swapping during runtime, but most of the domain and business layers were composed during build time and left alone while running.

4.) Since a user should be able to have entities/mappings in a separate bundle, does this imply that our OSGi activator must manage class loaders for every bundle?

5.) If "yes" for the above, are there performance considerations? Some of the OSGi environments I've been involved with in the past were huge. The OSGi class loader would either need to always iterate over all bundles to find a class/resource, or maintain its own Map. Or, am I over-thinking this?

6.) Class & package name collisions? It can and does happen (bundles A & B depend on different versions of C, Entities with the same package and classname, etc.). How should we handle them?