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 "ChangeLog" by MichaelBouschen
Date Mon, 16 Oct 2006 17:55:31 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 MichaelBouschen:
http://wiki.apache.org/jdo/ChangeLog

The comment on the change is:
trvial formatting changes

------------------------------------------------------------------------------
  
   1. 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.
  
-  1. In 6.4.3, change "Portable JDO applications must not depend on whether instances of
these classes are treat- 
- ed 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."
+  1. 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."
  
   1. In section 7.5, change "If the class is abstract, null is returned." to "If the class
is abstract, {{{JDOFatalInternalException}}} is thrown".
  
@@ -91, +90 @@

   1. 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 {{{jdoStateManager}}} is null, then
{{{JDOFatalInternalException}}} is thrown."
  
   1. 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. 
- {{{protected static int jdoGetManagedFieldCount () { 
+   {{{protected static int jdoGetManagedFieldCount () { 
  return jdoFieldNames.length;
  }
  }}} to {{{protected static int jdoGetManagedFieldCount () { 

Mime
View raw message