Instead of having database actions scattered in four (osgi) bundles, all doing there slightly different things. I want to create a (simple) OSGi bundle that is responsible for a
There are two ways I can think of to solve the classloading-issue.
Are you tied to a specific OSGi-Framework, or do you want to stay as compatible as possible? Or can you use equinox for your implementation? In Equinox you have a mechanism called Buddy Classloading. This addition allows you to increase the visibility of certain classes between different OSGi-Bundles. If you are interested in this topic, I would like to direct you to these two articles: Understanding how Eclipse plug-ins work with OSGi, Eclipse - a tale of two VMs (and many classloaders).
If you prefere to stay OSGi-implementation independent, then you might considre extracting your classes, that you wish to persist, into a separate bundle on which both the Hibernate-Bundle and your other bundles depend. That way, they all have access to the class definition of the persisted classes.