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 ------------------------------------------------------------------------------ || 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 || + || 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. || done || || [http://issues.apache.org/jira/browse/JDO-453 JDO-453] || - || 17 || In 12.6.8, section heading Explicit Detach, the sentence "If the parameter instance is detached, then JDO!UserException is thrown. " should be removed. || x || || || + || 17 || In 12.6.8, section heading Explicit Detach, the sentence "If the parameter instance is detached, then JDO!UserException is thrown. " should be removed. || done || || || - || 18 || In 12.6.8, add a note that serialization for storage using the serialized, serialized-element, serialized-key, or serialized-value metadata attributes does not create a detached instance. || x || || || + || 18 || In 12.6.8, add a note that serialization for storage using the serialized, serialized-element, serialized-key, or serialized-value metadata attributes does not create a detached instance. || done || || || || 19 || In 12.6.8, clarify the behavior of instances during serialization both with and without an active transaction. || x || || x || - || 20 || In 12.7.5, change public int setMaxFetchDepth(); to public int getMaxFetchDepth(); || x || || || + || 20 || In 12.7.5, change public int setMaxFetchDepth(); to public int getMaxFetchDepth(); || done || || || - || 21 || In 12.7.5, specify that getFetchGroups returns a read-only copy of the active Fetch Groups. || x || || x || + || 21 || In 12.7.5, specify that getFetchGroups returns a read-only copy of the active Fetch Groups. || done || || x || - || 22 || In 12.7.6, p. 127, change "A recursion-depth of 0 will fetch the whole graph of instances reachable from this field." to "A recursion-depth of -1 will fetch the whole graph of instances reachable from this field." || x || || || + || 22 || In 12.7.6, p. 127, change "A recursion-depth of 0 will fetch the whole graph of instances reachable from this field." to "A recursion-depth of -1 will fetch the whole graph of instances reachable from this field." || done || || || - || 23 || In 12.7.6 p. 129, change fetch-depth to recursion-depth in the example. || x || || || + || 23 || In 12.7.6 p. 129, change fetch-depth to recursion-depth in the example. || done || || || || 24 || In 14, add subqueries to permit e.g. select from Employee where this.salary > (select avg(salary) from Employee) || x || [https://issues.apache.org/jira/browse/JDO-446 JDO-446] || x || - || 25 || In 14.6.2 p. 159, the sectionheading "Methods" is not marked as a sectionheading. || x || || || + || 25 || In 14.6.2 p. 159, the sectionheading "Methods" is not marked as a sectionheading. || done || || || - || 26 || Add to 14.6.9: Projected SCOs are never owned, projected FCOs are always managed. Modifying unowned SCOs never has an effect on the database. Modifying FCOs no matter how you get them always has an effect if the tx commits. || x || || [http://issues.apache.org/jira/browse/JDO-390 JDO-390]|| + || 26 || Add to 14.6.9: Projected SCOs are never owned, projected FCOs are always managed. Modifying unowned SCOs never has an effect on the database. Modifying FCOs no matter how you get them always has an effect if the tx commits. || done || || [http://issues.apache.org/jira/browse/JDO-390 JDO-390]|| - || 27 || In 15.3, p. 187, the third paragraph, beginning "The field on the other side" and ending "in the next transaction", is duplicated and will be removed. || x || || || + || 27 || In 15.3, p. 187, the third paragraph, beginning "The field on the other side" and ending "in the next transaction", is duplicated and will be removed. || done || || || || 28 || In 15.3, add text to describe updating the other side of relationships where this side is deleted. This maintains referential integrity for delete as well as update. || x || || x || - || 29 || Add to 17.1.11 JDO!UserCallbackException extends javax.jdo.JDO!UserException || x || [https://issues.apache.org/jira/browse/JDO-447 JDO-447] || x || + || 29 || Add to 17.1.11 JDO!UserCallbackException extends javax.jdo.JDO!UserException || done || [https://issues.apache.org/jira/browse/JDO-447 JDO-447] || x || || 30 || In Chapter 18, add an xml element to specify the fetch plan to use for a query. || x || [https://issues.apache.org/jira/browse/JDO-448 JDO-448] || x || - || 31 || In 18.15.1, change "(e.g. a field of type Object can specify field-type=”Integer”)." to "(e.g. an element of type Object can specify element-type=”Integer”). || x || || || + || 31 || In 18.15.1, change "(e.g. a field of type Object can specify field-type=”Integer”)." to "(e.g. an element of type Object can specify element-type=”Integer”). || done || || || - || 32 || In Chapter 18, add to .jdo metadata: || x || || || + || 32 || In Chapter 18, add to .jdo metadata: || done || || || - || 33 || Add to 18.15.1 "The default for dependent-element is false." || x|| || || + || 33 || Add to 18.15.1 "The default for dependent-element is false." || done|| || || - || 34 || Add to 18.15.2 "The default for dependent-key is false." || x || || || + || 34 || Add to 18.15.2 "The default for dependent-key is false." || done || || || - || 35 || Add to 18.15.2 "The default for dependent-value is false." || x || || || + || 35 || Add to 18.15.2 "The default for dependent-value is false." || done || || || - || 36 || Change the last paragraph of 21.6 from "For Detachable classes, the results of restoring a serialized persistent instance graph is a graph of interconnected detached instances that might be attached via the attachCopy methods." to "For Detachable classes, the results of restoring a serialized persistent instance graph is a graph of interconnected detached instances that might be attached via the makePersistent methods." || x || || || + || 36 || Change the last paragraph of 21.6 from "For Detachable classes, the results of restoring a serialized persistent instance graph is a graph of interconnected detached instances that might be attached via the attachCopy methods." to "For Detachable classes, the results of restoring a serialized persistent instance graph is a graph of interconnected detached instances that might be attached via the makePersistent methods." || done || || || - || 37 || Change 21.13 from "Some methods require a non-null state manager. In these cases, if the jdoStateManager is null, then !IllegalStateException is thrown." to "Some methods require a non-null state manager. In these cases, if the doStateManager is null, then JDO!FatalInternalException is thrown." || x || || || + || 37 || Change 21.13 from "Some methods require a non-null state manager. In these cases, if the jdoStateManager is null, then !IllegalStateException is thrown." to "Some methods require a non-null state manager. In these cases, if the doStateManager is null, then JDO!FatalInternalException is thrown." || done || || || - || 38 || Change 21.21.7 Generated jdoGetManagedFieldCount sample implementation to avoid using the jdoFieldNames field that might be initialized after it is used during initialization of a subclass. (See ChangeLog for details.) || x || || || + || 38 || Change 21.21.7 Generated jdoGetManagedFieldCount sample implementation to avoid using the jdoFieldNames field that might be initialized after it is used during initialization of a subclass. (See ChangeLog for details.) || done || || || - || 39 || Add to Chapter 23, constants defined in the JDOPermission class. (See ChangeLog for details.) || x || || || + || 39 || Add to Chapter 23, constants defined in the JDOPermission class. (See ChangeLog for details.) || done || || || ||40 || JDK 1.5 changes || x || || || || 41 || Add to 6.3 a section requiring support for enum types, including subclasses of enum types. || x || || x || || 42 || Change in 12.6 signatures of the following !PersistenceManager methods to be generic. Note that these changes are source compatible with existing application programs. (See ChangeLog for details.) || x || [https://issues.apache.org/jira/browse/JDO-450 JDO-450] || x ||