ObjectDB ObjectDB

Internal Website Search

61-70 of 168 resultsRefresh
22

Selective merge/cascade of detatched entity

memory at all times, in a Detached state (I realise the implications here, there are good reasons ... would be for there to be some way to re-attach the detached salesman with some form of 'I promise I haven't changed ... improve things! My only remaining concern is that the reason the detached objects are kept in
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
0

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
0

setDetachmentOptions(options)

Method javax.jdo.FetchPlan FetchPlan setDetachmentOptions( int options ) Set options to be used during detachment. Options are DETACH_LOAD_FIELDS and DETACH_UNLOAD_FIELDS. Parameters: options - Since: JDO 2.0
0

preAttach(event)

) This method is called before a detached instance is attached, via the javax.jdo.PersistenceManager.makePersistent method. The source instance is the detached instance. This method is called before the corresponding AttachCallback.jdoPreAttach on the detached instance. Parameters: event - the attach event. Since: JDO 2.0
0

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
0

isDirty(pc)

transaction, or modified while detached return Boolean.TRUE. Instances known by the implementation ... the current transaction, or while detached. Since: JDO 2.0 See Also: StateManager.makeDirty
0

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
0

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
0

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"

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