What I don't understand is why my persistence bundle exports two EntityManagerFactory Services.
Component (44) provides: ------------------------------------------------------------ objectClass = javax.persistence.EntityManagerFactory org.apache.aries.jpa.container.managed = true org.apache.aries.jpa.default.unit.name = false osgi.unit.name = registry osgi.unit.provider = org.eclipse.persistence.jpa.PersistenceProvider osgi.unit.version = 1.0.0 service.id = 350 ---- objectClass = javax.persistence.EntityManagerFactory org.apache.aries.jpa.container.managed = true org.apache.aries.jpa.default.unit.name = false org.apache.aries.jpa.proxy.factory = true osgi.unit.name = registry osgi.unit.provider = org.eclipse.persistence.jpa.PersistenceProvider osgi.unit.version = 1.0.0 service.id = 351 ---- objectClass = xxx.Registry osgi.service.blueprint.compname = registryService service.id = 379 version = 1 ---- objectClass = org.osgi.service.blueprint.container.BlueprintContainer osgi.blueprint.container.symbolicname = org.oparo.services.registry.registry-component osgi.blueprint.container.version = 1.0.0 service.id = 389 Is this normal behaviour? If yes, which bundle is using those OSGi-services? -- View this message in context: http://karaf.922171.n3.nabble.com/Aries-error-No-transaction-currently-active-tp4025825p4025846.html Sent from the Karaf - User mailing list archive at Nabble.com.
