ObjectDB ObjectDB

Internal Website Search

81-90 of 126 resultsRefresh
4

Guessbook tutorial: Java EE 6 JPA Tutorial - Maven Project

_Generated__GuestDao__Intf____Bean__.persist(Unknown Source) at guest.GuestServlet.doPost(GuestServlet ... __GuestDao__Intf____Bean__.persist(Unknown Source) at guest.GuestServlet.doPost(GuestServlet.java:36
4

EntityManager JPA or JDO impl and different behavior

it populates the map in both. Because my project uses Spring to create the entity manager: <bean id ... ="persistenceUnitName" value="xPU" /> </bean> and in the test I load it directly I'm assuming
4

Cannot save or update entity on Spring App

] (error 611) Here's how I set up the transactionManager: @Bean public JpaTransactionManager ... (); return transactionManager; } Ieodaq Daniele Lotti Also, I've got this as a requirement: @Bean
4

How to track memory leak with ObjectDb.

objectdb.MST containing some trace of my entities beans. It seems objectdb keep in memory some ... ( i observed that it represent some data of my entities beans ). xirt Sylvain This shows the page
3

ObjectDB without javax.persistence

(ProfileApplicationServiceImpl.java:131) at com.btc.ep.base.ui.session.SessionManager.createNewSession(SessionManager
3

virtual servers and one file

remote sessions. As far as I understand it is not the problem of less memory of the physical or
3

evictAll() behavior

whereas L2 is more like a session cache? andrewmcveigh Andrew McVeigh The L1 cache is per EntityManager
0

com.objectdb.o.InternalException: java.lang.ArrayIndexOutOfBoundsException: null:

.entity.Source) javax.ejb.TransactionRolledbackLocalException: Exception thrown from bean at com.sun ... Source) at com.greensoft.greenstar.ejb.ext.__EJB31_Generated__ExtGreenStarRequestBean__Intf____Bean
0

ObjectDB 2.3.1

a Doctor and Replication regression (Type session exceeds timeout). Removed Conflicting modifiers validation check and error message.
0

Threaded Test - Failed to commit transaction: Unexpected internal exception

them. This session helped fixing some important issues in ObjectDB, and apparently you are facing now

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