db-jdo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Jdo Wiki] Trivial Update of "CurrentDevelopment" by CraigRussell
Date Wed, 10 Oct 2007 19:06:53 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Jdo Wiki" for change notification.

The following page has been changed by CraigRussell:
http://wiki.apache.org/jdo/CurrentDevelopment

------------------------------------------------------------------------------
  || 1 || In 5.4.1, Compound Identity should be updated to reflect that for key fields of
reference types, the type of the key field is the reference type in the class but the oid
of the reference type in the oid class. || done || || done ||
  || 2 || In Table 2: State Transitions, the transition for a transient-dirty instance during
commit with !DetachAllOnCommit = true should be to transient-clean. Also, state changes need
to be added for detach methods and serialization. || [http://issues.apache.org/jira/browse/JDO-456
JDO-456]|| || [http://issues.apache.org/jira/browse/JDO-456 JDO-456]||
  || 3 || In 5.5.8 and 5.5.9, detachCopy should be removed from the list of methods that throw
exceptions if applied to detached-clean or detached-dirty instances. || done || || ||
- || 4 || In 6.4.3, change "Portable JDO applications must not depend on whether instances
of these classes are treated as SCOs or FCOs. " to "Portable JDO applications must not depend
on SCO or FCO uniquing behavior, nor on the storage mechanism in the datastore. Portable applications
may use the same instance of these classes as field values in any persistence-capable class
instance." || done || ||[http://issues.apache.org/jira/browse/JDO-397 JDO-397] ||
+ || 4 || In 6.4.3, change "Portable JDO applications must not depend on whether instances
of these classes are treated as SCOs or FCOs. " to "Portable JDO applications must not depend
on SCO or FCO uniquing behavior, nor on the storage mechanism in the datastore. Portable applications
may use the same instance of these classes as field values in any persistence-capable class
instance." [http://issues.apache.org/jira/browse/JDO-397 JDO-397]|| done ||  ||  ||
  || 5 || In section 7.5, change "If the class is abstract, null is returned." to "If the
class is abstract, JDO!FatalInternalException is thrown". || done || || ||
  || 6 || In section 7.5, add public byte fetchByteField(int fieldNumber); to !ObjectIdFieldSupplier.
|| done || || ||
  || 7 || In section 7.5, add public byte storeByteField(int fieldNumber, byte value); to
!ObjectIdFieldConsumer. || done || || ||

Mime
View raw message