Fast Object Database for Java - with JPA/JDO support

Internal Website Search

61-70 of 169 resultsRefresh
5

preDetach(event)

the detached copy is made. It is called before the method DetachCallback.jdoPreDetach is called on the instance to be detached. Parameters: event - the detach event. Since: JDO 2.0
5

postDetach(event)

after the detached copy is made. It is called after the method DetachCallback.jdoPreDetach is called on the detached instance. Parameters: event - the detach event. Since: JDO 2.0
5

makeTransientAll(pcs, useFetchPlan)

detachCopy, the instances are not detached; there is no detachment information in the instances. The instances to be made transient do not need to implement the javax.jdo.spi.Detachable interface
5

javax.jdo.annotations.PersistenceCapable

for persisting this class or interface. Default value: "" Since: JDO 2.1 String detachable Whether this class or interface is detachable. Whether this class or interface is detachable. Default value
5

makeTransientAll(pcs, useFetchPlan)

detachCopy, the instances are not detached; there is no detachment information in the instances. The instances to be made transient do not need to implement the javax.jdo.spi.Detachable interface. Parameters
5

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

EITHER: the transparent activation is failing AND/OR: entities are becoming detached. http://www.objectdb.com/java/jpa/persistence/detach I can't find out how to test where an entity is detached. http://www.objectdb ... Kelly My feeling (before running your application) is that indeed detachment might be the problem
4

getDetachedInstance()

Method javax.jdo.listener.InstanceLifecycleEvent Object getDetachedInstance() Returns the detached instance involved in the event. Returns: The detached instance involved in the event, or null if there was none. Since: JDO 2.0 See Also: "Section 12.15, Java Data Objects 2.0 Specification"
4

postAttach(event)

Method javax.jdo.listener.AttachLifecycleListener void postAttach( InstanceLifecycleEvent event ) This method is called after a detached instance is attached, via the javax.jdo.PersistenceManager ... ; the target instance is the detached instance. This method is called after the corresponding
4

javax.jdo.listener.AttachCallback

.makePersistent on the detached instance before the copy is made. This method is called during the execution of javax.jdo.PersistenceManager.makePersistent on the detached instance before the copy is made. Since: JDO 2.0
4

javax.jdo.ObjectState

the object states for JDO instances. Since: JDO 1.0 ObjectState DETACHED_CLEAN Since: JDO 1.0 ObjectState DETACHED_DIRTY Since: JDO 1.0 ObjectState HOLLOW_PERSISTENT_NONTRANSACTIONAL Since: JDO 1.0

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