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] Update of "CurrentDevelopment" by CraigRussell
Date Fri, 05 Jan 2007 22:26:48 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

------------------------------------------------------------------------------
  The task to adapt the JDO sources to the new apache license policy is completed, see FixingLicenseHeader
for details.
  
  || 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. || done || || 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 || || [http://issues.apache.org/jira/browse/JDO-457
JDO-457] ||
  || 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] ||
@@ -23, +23 @@

  || 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. || 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.
|| done || || ||
- || 19 || In 12.6.8, clarify the behavior of instances during serialization both with and
without an active transaction. || x || || x ||
+ || 19 || In 12.6.8, clarify the behavior of instances during serialization both with and
without an active transaction. || [http://issues.apache.org/jira/browse/JDO-456 JDO-456]||
|| [http://issues.apache.org/jira/browse/JDO-456 JDO-456]||
  || 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. || done || || x ||
+ || 21 || In 12.7.5, specify that getFetchGroups returns a read-only copy of the active Fetch
Groups. || done || || [http://issues.apache.org/jira/browse/JDO-458 JDO-458]||
  || 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. || 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 ||

Mime
View raw message