Home » Search

About change

71-80 of 200Refresh
JDO Doc
3

javax.jdo.InstanceCallbacks

four other interfaces, without changing any of the methods or semantics. This allows fine-grained control ... other instances on changes to state. The persistent instance might be in a list of managed instances. When the persistent instance is made hollow, it can no longer generate change events
JDO Doc
3

javax.jdo.spi.StateManager

identity of the calling instance. If the JDO identity is being changed in the current transaction ... the object representing the JDO identity of the calling instance. If the JDO identity is being changed in the current transaction, this method returns the current identity as changed in the transaction
JDO Doc
3

makePersistent(pc)

instance changes to the cache. It must be called in the context of an active transaction, or ... callbacks and attach life cycle listeners are called. During application of changes of the detached state, if the JDO implementation can determine that there were no changes made during detachment
JDO Doc
3

getObjectId(pc)

state of the instance, and changing it does not affect the JDO identity of the instance ... the application, and those that are managed by the data store. If the object identity is being changed in ... of the class used to manage identity internally. Therefore, if the application makes a change
Result
3

java.lang.Throwable

the flexibility to change the implementation of the upper layer without changing its API (in particular, the set ... array is copied by this call; changes in the specified array after the method invocation returns
JDO Doc
3

javax.jdo.JDOHelper

are able to detect changes made to their fields. However, if a reference to an array is given ... of the change. This API allows the application to notify the instance that a change was made to a field
JDO Doc
3

javax.jdo.spi.StateInterrogation

and field dirty. Normally, PersistenceCapable classes are able to detect changes made to their fields ... , then the persistent instance is not aware of the change. This API allows the application to notify the instance that a change was made to a field. Instances unknown by the implementation
JDO Doc
3

jdoMakeDirty(fieldName)

this instance and this field dirty. Normally, PersistenceCapable classes are able to detect changes ... , and the array is modified, then the persistent instance is not aware of the change. This API allows the application to notify the instance that a change was made to a field. The field name
JDO Doc
3

makeDirty(pc, fieldName)

changes made to their fields. However, if a reference to an array is given to a method outside the class, and the array is modified, then the persistent instance is not aware of the change. This API allows the application to notify the instance that a change was made to a field. Transient instances
JDO Doc
3

makeDirty(pc, fieldName)

to detect changes made to their fields. However, if a reference to an array is given to a method outside the class, and the array is modified, then the persistent instance is not aware of the change. This API allows the application to notify the instance that a change was made to a field. Instances