ObjectDB ObjectDB

Internal Website Search

71-80 of 200 resultsRefresh

JPA - ExceptionInInitializerError when creating EntityManager

.EntityManagerFactoryImpl@ffa7e1 EntityManager emTemp = emf.createEntityManager(); TypedQuery<EmailSettings ... .createEntityManagerFactory("myDBPU"); javax.persistence.EntityManager em = emf.createEntityManager(); try { Object

javax.persistence.PersistenceException: No Persistence provider for EntityManager named in Karaf 4.0.7 and OSGi DS test

.persistence.PersistenceException: No Persistence provider for EntityManager named objectdb://localhost:6136

EntityManager.merge gives EntityNotFoundException

Just started using objectdb (2.3.4). Calling EntityManager.merge for a new (non-managed) object gives EntityNotFoundException. I am perplexed by this. See attached test case. Thanks for your assistance. Full error output is: Exception in thread "main" [ObjectDB 2.3.4] javax.persistence

Executing JUnit "all tests" throws "Object ... belongs to another EntityManager" Exception

#7' belongs to another EntityManager [Symbol:7] When I change the order in which the test runs (by

multi EntityManager with Spring Boot, but 'Too many persistable types (>10)

I'm trying to use two EntityManager with Spring Boot, but no luck with 'Too many persistable types (>10) - exceeds evaluation limit' at second database. My purpose is converting database (converting model entity. same class name but different package). Single application with Spring-Boot 2.1.8

"No Persistence provider for EntityManager" in OSGI bundle.

provider for EntityManager named $objectdb/myDB.odb at javax.persistence.Persistence

Creation of several EntityManager is slower

Creation of several EntityManager is slower

DB persist operation results are not available for another Thread/EntityManager immdiately

Hello, we have following situation: The EntityManagerFactory is always opened and won't be closed. Thread A with its own EntityManager persists entities and commits the entities successfully. Thread B runs afterwards also with its own EntityManager and tries to load the persisted entities by


objects into an EntityManager. Updating the relevant entity object fields within an active transaction ... them, but it should be used cautiously because bypassing the EntityManager may break its synchronization with the database. For example, the EntityManager may not be aware that a cached entity object in

Locking in JPA

another EntityManager) since it was retrieved by the current updater. Optimistic locking ... another EntityManager instance) currently holds a PESSIMISTIC_WRITE lock on that database object. A PESSIMISTIC ... .lock(e1, lockMode1); em2.lock(e2, lockMode2); em1 and em2 are two EntityManager instances

Getting Started

ObjectDB is very easy to use. Follow the Getting Started Tutorial and the Quick Tour manual chapter and in minutes you may be able to write and run first Java programs against ObjectDB.

Prior knowledge or experience in database programming (SQL, JDBC, ORM, JPA, etc.) is not required, but some background in using the Java language is essential.

Need Help?

  1. Search ObjectDB website
  2. Read the FAQ
  3. Follow the Tutorials
  4. View or post in the forum
  5. Search or file an issue
  6. Contact support