About access

api-jdo

javax.jdo.JDOUserCallbackException

This class represents exceptions caused by exceptions thrown during execution of callbacks or listeners.(Exception of JDO)

 
api-jdo

javax.jdo.JDOUserException

This class represents user errors that can possibly be retried.(Exception of JDO)

 
api-jdo

javax.jdo.JDOFatalException

This class represents exceptions that are fatal; that is, the condition that caused it cannot be bypassed even if the operation is retried.(Exception of JDO)

 
api-jdo

javax.jdo.JDOFatalInternalException

This class represents errors in the implementation for which no user error handling is possible.(Exception of JDO)

 
forum_thread

Where Does ObjectDB Block/Lock?

These are questions asked in the context of the proposed architecture described in the forum thread titled, "Sample JDO Architecture for Follow Up Questions".   Questions about blocking/locking.  With my PersistenceManager multiThreaded=true architecture, I desire to know where ObjectDB is actually blocking/locking so I might adapt to achieve better concurrency. 1) Where are locks when accessing PersistenceManager by multiple threads? 2) Does it lock at PersistenceManager.currentTransaction()? ... are synchronized so multiple threads should be able to access and use a shared PersistenceManager instance safely. ObjectDB ...

 
api-jdo

javax.jdo.JDOOptimisticVerificationException

This class represents optimistic verification failures.(Exception of JDO)

 
forum_thread

_UserException: Attempt to open a database file '...' that is currently in use

I have an application which runs correctly in NetbeansIDE but after building it, it won't just run sometime, the app stop responding to event at a particular point. I was able to reproduce this issue while running the jar file in command line and I got this exception which I have it stack attached here http://i.stack.imgur.com/IH8XZ.jpg ... Page... by one run before another attempt to access it by another run, or use client-server mode. ...

 
forum_thread

Post-compilation enhancement vs Automatic Run-time enhancement

We are getting massively different results on field loading between explicit post-compile enhancement and automatic run-time enhancement. Testing exactly where and when the results are different for our demo web app is a very time consuming task, and very difficult, it means testing literally 100s of user interfaces (noting we get different results OUTSIDE THE JAVA SERVER FACES BACKING BEAN LAYER depending on the enhancement stragegy). Can you please explain how this could possibly be so ? ... the 2 enhancement techniques giving identical data access results ? --- Webel IT Australia, "The Elements of ... enhance non entity classes. This may be relevant if you access persistent fields from non entity classes. Could you please ...

 
api-jdo

javax.jdo.JDODataStoreException

This class represents data store exceptions that can be retried.(Exception of JDO)

 
api-jdo

javax.jdo.JDOReadOnlyException

This class represents exceptions caused by an attempt to update a datastore when the PMF was created as "read-only".(Exception of JDO)