About EntityManager

191-200 of 200Refresh
Forum
2

Field not persisted in abstract class with two level of nesting

.Entity; import javax.persistence.EntityManager; import javax.persistence.Persistence; @Entity ... main(String[] args){         EntityManager em = Persistence.createEntityManagerFactory("$objectdb/db ... .EntityManager; import javax.persistence.Persistence; @Entity public class MHD2 implements Serializable
Forum
2

find() delay

a transaction of em. Maybe different EntityManager instances are used and the L2 cache is enabled. L2 ... .createEntityManagerFactory(             "$objectdb/db/test.odb");         EntityManager em = emf.createEntityManager ... ");   EntityManager em = emf.createEntityManager();   EntityTransaction trans = em.getTransaction();   int
Forum
2

Finding out the JPA provider

Do you have any preferred way of finding out whether ObjectDb is my EntityManager's JPA Provider? I ... of the PeristenceUnit were visible in one of the Properties sets returned by the EntityManager and EntityManagerFactory, but its not. So I am left with EntityManager.getDelegate() instanceof com.objectdb.jdo
Issue
2

Issues with JDO Casting & Full Qualified Names

.persistence.Embeddable; import javax.persistence.Entity; import javax.persistence.EntityManager ... .createEntityManagerFactory("objectdb:$objectdb/db/test4.tmp;drop");   EntityManager em = emf ... .persistence.EntityManager; import javax.persistence.EntityManagerFactory; import javax.persistence
Forum
2

Multi-thread access to single EM's entities

; import javax.persistence.EntityManager; import javax.persistence.EntityManagerFactory; import javax ... .createEntityManagerFactory(             "objectdb:/home/kevin/threads-test.odb");         EntityManager em = emf ... in ObjectDB's EntityManager and associated classes are synchronized, so even if you do use the same
Forum
2

multiple LEFT JOINs do not work as expected

(                 "objectdb:test.tmp;drop");         EntityManager em = emf.createEntityManager ... ();     }         private static Node persistTree(EntityManager em, Node parent, int depth) {         Node node ... .createEntityManagerFactory( "objectdb:test.tmp;drop"); EntityManager em = emf
Forum
2

Object DB vs EclipseLink/TopLink: Unloaded relationships in detached entities

(and so lazy loading would initially work), they become detached once the EntityManager under control ... with an extended EntityManager as described here: Extended Persistence Context in Stateful Session Beans ... only once, and not in any way related to extended EntityManager or persistence context. - "container
Issue
2

objectdb-2.6.9_06: Extended Persistence Context fails: 'Attempt to begin a new transaction when a transaction is active'

All_ { @PersistenceContext(type = PersistenceContextType.EXTENDED)//! protected EntityManager ... = PersistenceContextType.EXTENDED)//! protected EntityManager em; /* public ... a transaction using a closed EntityManager (error 525) at com.objectdb.jpa.EMImpl.afterCompletion
Forum
2

On initialisation of lists: impact on migration from EclipseLink to ObjectDB

a List implementation into the List field to be initialise it during EntityManager.persist(). So in ... > blocks;         //EclipseLink: no need to init, will be done by EntityManager.persist ... } } Then used as: @PersistenceContext private EntityManager em; ..     HasListOfBlocks h = new
Forum
2

Possible issue with LAZY Loading

is accessible if entity objects are managed by an open EntityManager, but it is fetched lazily when needed. You do see a difference (in addition to performance differences) when the EntityManager is closed ... either. Ok, so then I believe Lazy loading is broken, cause if I close the entityManager without calling