ObjectDB Database Search

; import javax.persistence. EntityManager ; import javax.persistence.EntityManagerFactory; import ... ;  .createEntityManagerFactory("objectdb:$objectdb/db/test.tmp;drop");   EntityManager em;   for (int i = 0; i

The code I have a RecordDao stateless java bean :  @Stateless public class RecordDao { private EntityManagerFactory emf; private EntityManager em; public RecordDao() { } @PostConstruct public ... the EntityManagerFactory and the EntityManager explicitly, but let the application server

: No Persistence provider for EntityManager named pilots.odb at javax.persistence.Persistence ... with " No Persistence provider for EntityManager named $objectdb/db/pilots.odb" as the cause.   When I

.createEntityManagerFactory("TESTDB.odb");         EntityManager emg =EMF ... ("TESTDB2.odb");         EntityManager emg =EMF

them when it creates new EntityManager instances. See this manual page for more information on working with EntityManagerFactory  (which manages the connection pool) and EntityManager (which represents

EntityManager em; @PersistenceContext(unitName = "mysqlPU") private EntityManager em1; @Transactional

.PersistenceException: No Persistence provider for EntityManager named xxx Upon closer examination, isn't javax ... == null) { /* 85 */ throw new PersistenceException("No Persistence provider for EntityManager named

Test { private final EntityManagerFactory emf; private final EntityManager em; public Test() { emf

/test.tmp;drop");         EntityManager em = emf

;         EntityManager em = null;      

= (EntityManagerFactory) servletContext.getAttribute("emf"); EntityManager em = emf.createEntityManager(); Person

the EntityManagerFactory (or is it the EntityManager ?) where to store the log-file

Would it make sense to call entityManager .merge(o) for each of the objects returned to get the child

one  EntityManagerFactory per application, with multiple  EntityManager instances for multiple database connections. support Support

, 8.0, 8.0 Merge it            EntityManager em = getEM();  

Christian Code we run:     private void registerTypes() { try { EntityManager em

Hey, I have a problem to use SF with an Extended Persistence Context Regarding to Transactions. The need for an extended persistence Context emerges for the need to create queries in advance for fast execution so I need to store the queries and I need an EntityManager that doesn't get closed

" ; EntityManagerFactory emf = Persistence . createEntityManagerFactory ( PATH ); EntityManager em = emf

;    EntityManager em = emf.createEntityManager();       

to the EntityManager metamodel for caching some oft-used information in an application-wide

/test.odb");         EntityManager em = emf.createEntityManager

; EntityManager em = emf.createEntityManager();         em

EntityManager em = SingleManager.getEntityManager(); public void read(){   int iCnt = 10;  

; EntityManager em = emf.createEntityManager();         em

; EntityManager em = emf.createEntityManager();            

Hello, i have a problem with a UPDATE statement. When i run the code without WHERE clause the cod is executed, but when i attach the WHERE the program stop there. The code looks like this. EntityManager em = emf.createEntityManager() ; em.getTransaction().begin() ; EntityManager updateEm = emf

at this point is performing a delete query for all entity objects that the database contains: EntityManager em

( "objectdb://SE101388:6136//SE101352:6136/WorkflowHistory.odb;user=...;password=..."); EntityManager em

");         EntityManager em = emf.createEntityManager();  

Hello, I have a tree of entity classes that reference others using Cascade.ALL in combination with FetchType.LAZY. If I now delete a root entity using EntityManager .remove all leaf nodes will not be deleted. This only applies to the leaf nodes. If I add an additional the behaviour changes