I think it should be possible to use this example as a starting point. I’m afraid getting this dynamic behavior to work is ridiculously complex (not simple!), so if you build on top of this example I would make only very minor changes between running a full test suite and checking in the changes.

The version of Hibernate I used is a little dated now, and there may be other persistence frameworks that are better suited for OSGi type development.

I think you are right. The big problem was (as I remember it from almost 2 years ago), to share the same DynamicConfiguration among bundles (all DynamicSessionFactory instances refer to the same instance of DynamicConfiguration). Looking at it again now it seems that the code could just as well have referenced a single DynamicSessionFactory instance. At the moment I cannot see why that wouldn’t work.

-Hans

While going though the code I found that “com.notehive.osgi.hibernate_samples.session.DynamicSessionFactory” has been configured and instantiated as a bean “dynamicSessionFactory” (through bundle-context.xml files) in hibernate-session and model-a and model-b. Are we creatinging multiple instances of DynamicSessionFactory here?

If yes, could you please explain the use of it as I beleive that we need only one “dynamicSessionFactory” from hibernate-session bundle which will be consumed by other bundles and .

Thanks,
Amit

I’m using your example as base (hibernate_session, model_a projects) and created brand new projects very similar to that. And I also use BND plugin to generate jar files. I am using Spring DM server, I started the server, copied the hibernate_session equivalen project to pickup folder, once I see “Deployed … completed” message, then I deployed “model_a” equivalent project and I also same “Deployed … completed” message but I do not see the bundleChanged event fired. I also checked out ss and I could see that both bundles are in ACTIVE state. What might be the problem with this approach ? Could you please help me with this ?

(I) Bundle Exporting EntityManagerFactory
I have used a singleentitymanager factory and have exported it as an OSGI service

(II) Bundles with Entities, importing EntityManagerFactory
(a) Imported EntityManagerFactory into other bundles using osgi:reference element.
(b) Also set the FragmentHost set to the bundle exporting EntityManagerFactory. The PU bean is otherwise not visible to this bundle.
(c) Note the persistence.xml file need to have the managed class names. At the moment hibernate is not able to scan the enitties in the bundle.
(d) have postProcessPersistenceUnitInfo() overridden in DefaultPersistenceUnitManager to update the managed classes from the old pui. When more then one bundle exports persistence.xml the latest overrides the rest.

Please let me know if there is better way to set the managed clasess than specifying the persistence.xml.
loedolff your work on this has primarily guided by to reach this far.

(I) Bundle Exporting EntityManagerFactory
I have used a singleentitymanager factory and have exported it using

(II) Bundles with Entities, importing EntityManagerFactory
(a) Imported EntityManagerFactory into other bundles.
(b) Also set the FragmentHost set to the bundle exporting EntityManagerFactory.
(c) Note the persistence.xml file need to have the managed class names.
Also have postProcessPersistenceUnitInfo() overridden in DefaultPersistenceUnitManager to update the managed classes from the old pui.

Please let me know if there is better way to set the managed clasess than specifying the persistence.xml.
loedolff your work on this has primarily guided by to reach this far.

I just gone through your post it looks very helpful, here I have Some doubts, first of all I want try out an example using JPA with hibernate.

My scenario is like this, My application built up with many bundles, and each bundle will be a module of my application, so when ever I deploy any bundle , that particular module should be added to the Application, and its corresponding DB table s should be get created in the Application DB. For this I approached like this, In each bundle’s Manifest folder I just kept the persistence.xml, and I am using Datasource as an OSGi service, I created an entity manager factory for each bundle in respective bundle (as it has to execute the persistence.xml), here is my problem like,Is it possible to use a singleentitymanger factory to execute the each bundles persistence.xml at the time of deployment of each bundle.

I red your article with great interest as I am currently starting a project on Equinox/Spring DM and wish to use JPA with hibernate.
I tried to download the code from SVN, but a username/password is required.
Could you provide me the credentials. Regards, christian.