[Jdo Wiki] Update of "CurrentDevelopment" by CraigRussell

[Apache Wiki <wi...@apache.org>]

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

------------------------------------------------------------------------------
  This page list the work planned for the JDO 2.1 Maintenance Release. The work may involve updating the specification, changing the api, and/or adding tests or modifying tests in the TCK. 
  
  || Number || Task || Spec changes || API changes || TCK changes ||
- || 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. || x || || x ||
+ || 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 || || x ||
  || 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. || x || || x ||
- || 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. || x || || ||
+ || 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." || x || || ||
+ || 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] ||
- || 5 || In section 7.5, change "If the class is abstract, null is returned." to "If the class is abstract, JDO!FatalInternalException is thrown". || x || || ||
+ || 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. || x || || ||
+ || 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. || x || || ||
+ || 7 || In section 7.5, add public byte storeByteField(int fieldNumber, byte value); to !ObjectIdFieldConsumer. || done || || ||
- || 8 || In Chapter 8, add after class JDOHelper {public JDOHelper(); For some usage patterns, an instance of JDOHelper on which to invoke methods is preferable to the use of static methods. For this purpose, a public constructor is provided. || x || [https://issues.apache.org/jira/browse/JDO-444 JDO-444] || ||
+ || 8 || In Chapter 8, add after class JDOHelper {public JDOHelper(); For some usage patterns, an instance of JDOHelper on which to invoke methods is preferable to the use of static methods. For this purpose, a public constructor is provided. || done || [https://issues.apache.org/jira/browse/JDO-444 JDO-444] || ||
  || 9 || In Chapter 8, add a convenience method that returns a !PersistenceManager proxy that can be used in web and ejb containers to dynamically bind to the transaction-associated !PersistenceManager. || x || [https://issues.apache.org/jira/browse/JDO-445 JDO-445] || ||
  || 10 || In Chapter 9, add section on managing date formatting for !ObjectIdentity constructors. public synchronized void registerDateFormat(java.text.!DateFormat df); || x || || ||
- || 11 || In 9.4, add method to retrieve persistence-capable classes that have been registered. public java.util.Collection getRegisteredClasses(); || x || || ||
+ || 11 || In 9.4, add method to retrieve persistence-capable classes that have been registered. public java.util.Collection getRegisteredClasses(); || done || || ||
- || 12 || In 9.5, add method to verify that the class is authorized to be a state manager. public static void checkAuthorizedStateManagerClass(Class smClass); || x || || ||
+ || 12 || In 9.5, add method to verify that the class is authorized to be a state manager. public static void checkAuthorizedStateManagerClass(Class smClass); || done || || ||
- || 13 || In 9.5, add method to register multiple state manager classes. public static void registerAuthorizedStateManagerClasses(java.util.Collection smClasses) throws !SecurityException; || x || || ||
+ || 13 || In 9.5, add method to register multiple state manager classes. public static void registerAuthorizedStateManagerClasses(java.util.Collection smClasses) throws !SecurityException; || done || || ||
  || 14 || In Chapter 11, add properties for configuring !PersistenceManagerFactory that are consistent with JPA specification of !TransactionType and Persistence Unit Name. || x || [https://issues.apache.org/jira/browse/JDO-449 JDO-449] || ||
  || 15 || In Chapter 12, specify the behavior of !PersistenceManager if it extends Serializable and writeObject is called. || x || || x ||
  || 16 || In 12.6.6, clarify that a JDO!UserException will be thrown when invoking newInstance: if a class is not persistence-capable, or does not declare a public no-args constructor; if an interface is not persistence-capable or declares methods that are not defined as persistent properties; if an abstract class is not persistence-capable or declares abstract methods that are not defined as persistent properties. || x || || x ||