Hi,
I have a bit of problem using org.apache.aries.jpa.container.context. Depending on the bundle start order either the original EntityManagerFactory service is picked up or not. I created a sample that is available at https://docs.google.com/open?id=0B3s_FOEzneQdVG1xLW5oakVkVUk To reproduce: - run startup (equinox starts with the bundles and you have a console. In windows due to some reason you cannot see on the console what you type) - In the console with the "ss" command you can see that every non-fragment bundle is active - With the "services javax.persistence.EntityManagerFactory" you can see that the original EntityManagerFactory service is created To solve: - Delete the "org.eclipse.osgi" folder under configuration - Take the "reference\:file\:lib/org.apache.aries.jpa.container.context-1.0.0.jar@start, \" line in the config.ini file to be one of the first ones - Run startup - Everything works as expected If you need any source I can provide it however I think the only two bundles that are related are the jpa.blueprint and jpa.container.context. You may realize that a custom developed jpa.container bundle is used in this sample but I think it is nothing to do with the problem itself. Thanks and regards, Balazs Zsoldos
