Internal Website Search

171-180 of 200 resultsRefresh

Connection is closed Caused by:

when the database is creating an EntityManager.   I have checked throughout my code to ensure that  all instances of EntityManager that I create ... ;   }     } } Notice that the EntityManager

How to Remove records from many to many relationship tables in JPA

(conclusion.getId()); public void removeConclusions(Long id) { entityManager = dbConn.getConnection(); Conclusion conclusion = entityManager.find(Conclusion.class, id); entityManager.getTransaction().begin(); entityManager.remove(conclusion); entityManager

NoSuchFieldError: __odbTracker on NetBeans 7.3 + JBoss 7.1.1

>city.setName("Москва"); person.setCity(city); entityManager.persist(city); entityManager.persist(person); The exception: entityManager.persist(person); City city = new City

Unexpected behaviour upon update. Bug?

;    Persistence.createEntityManagerFactory("ODB.odb"); EntityManager em ... is cached in the EntityManager as a managed entity object and it is returned with the update from the query. Changes in one EntityManager

Memory Leak?

">EntityManager instances (PMImpl). The other instances are probably hold by the EntityManager instances, so the question is why the EntityManager instances are not released. The code that you posted

Transaction isolation support?

> Every EntityManager manages its own memory objects (which represent database objects). Therefore, if an entity object is retrieved by one EntityManager and then updated in the database by another EntityManager, the first

Embedding ObjectDB on server application

for EntityManager named test.odb Shouldn't the method automatically create a database ... : No Persistence provider for EntityManager named objectdb:$objectdb/test.odb Description: Error during event handling: javax.persistence.PersistenceException: No Persistence provider for EntityManager named

spuriously objectdb objects have null references

> we are using a separate entityManager per thread and have a central point where we encapsulated all the needed entitymanager methods and protected them with synchronized like:   EntityManager threadEntityManager){ synchronized(lockBegin){ try

new objects not available in mappedBy associations

and before commit, if your EntityManager is set to use EntityManager? ps: setting FlushModeType.AUTO in the EntityManager resulted in a huge exception message. dmoshal David Moshal > Hmm, I

Feature suggestion: auto-detection of entities via persistence.xml extension

I am encountering problems (complexities) with EntityManager registration of entities ... :// Example ... ObjectDB ? Q2: Does it make any difference to the EntityManager whether one performs compile