ObjectDB ObjectDB

Internal Website Search

151-160 of 200 resultsRefresh

Mismatch client-server protocol prefix

. It could be because of concurrent use of the same connection and sockets (i.e. same EntityManager) by two concurrent threads. ObjectDB synchronizes use of EntityManager by different threads, but maybe there is an uncovered ... a socket from a closed EntityManager is still used after the EntityManager is closed after its resources

Query results are not up to date for entities, not primitives

objects and then updating 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 ... . Therefore, it is a good practice to use a separate EntityManager for UPDATE queries." support Support Ok

Conflicting modifiers .... (javax.persistence.Id, javax.persistence.ManyToOne)

javax.persistence.Basic; import javax.persistence.Entity; import javax.persistence.EntityManager ... ") }) public class Container { public static Container getInstance(EntityManager em) { Container c ... , EntityManager em) throws TestException { if (lastInstanceInMap == null) { lastInstanceInMap

Visibility of changes in Transaction is not visible to a JPA QL Query

getInstance(EntityManager em) {   Singleton c = em.find(Singleton.class, "1");   if (c == null) {    c ... .lang.Integer lastInstance; public void generateItems(EntityManager em, int howMany ... (EntityManager em) {   TypedQuery<Long> q = em.createQuery("SELECT COUNT(x) FROM Item x", Long.class

Problem on JPA Merge Entity.

Hello, I have a problem with the EntityManager.merge() function. I set a property value ... ErgoDaoJpa implements IErgoDao { @PersistenceContext private EntityManager entityManager ... , DaoException { entityManager.persist(ergoClass); } public void updateErgoClass

Entity listener - event instead of object

database. I can't find the nice way to use EntityManager in EntityListener. Because of that, I can't ... . Please be more specific regarding the technical question. Do you need to obtain an EntityManager from ... to an EntityManager. support Support I know about this feature request and I'm already subscribed. The main

openejb jpa jaas module

javax.persistence.EntityManager; import javax.persistence.EntityManagerFactory; import javax ... EntityManager entityManager; protected Map<String, ?> sharedState = new HashMap ... ) options.get("url")); entityManager = entityManagerFactory.createEntityManager

Filename.odb$ Persisting Issue

("$objectdb/db/payrollDB - Copy0.odb"); public  static EntityManager departmentDB = emf.createEntityManager(); public  static EntityManager employeeDB = emf.createEntityManager(); public  static EntityManager paygradeDB = emf.createEntityManager(); public  static EntityManager programDB = emf


seems to work around the problem. In the error version I'm keeping the entityManager at the thread level ... version a new entityManager is opened & closed for each action (load, remove, etc). When an update has occurred the actions are now: Open a new EntityManager Open a new transaction Merge the updated object

Once served to JSF page via @EJB query bean, many list fields are null (but same query ok after fresh persist in @PostConstruct)

TestQuery { @PersistenceContext private EntityManager em; public List<Element> findElements ... . Your TestQuery class uses a transaction scope EntityManager (the default as explained ... findElements, etc. 2. Switch to extended scope EntityManager By doing that you prevent detachment on exit

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