About EntityManager

191-200 of 200Refresh
Forum
1

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
1

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
1

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
1

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
1

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
1

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
1

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
1

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
Forum
1

Problem undeploying Glassfish3.1.1 web application cleanly

EntityManager injection, using the undeploy feature under the Glassfish server node  of Netbeans7.1 ... (which also uses @PersistenceContext EntityManager injection)? > Is it possible to get this exception with the simple tutorial GuestBook example (which also uses @PersistenceContext EntityManager
Forum
1

problem with lazy loading - unittest project attached

that when the test is not annotated with @Transactional - an ad hoc EntityManager instance is prepared for running findOne, and when the query execution completes that EntityManager is closed and the result object ... should have his own transaction. spring does not allow me to call entityManager.getTransaction().begin()/commit