| Javadogs, We need a way to determine whether a JDO implementation supports various features that are not yet listed in 11.6. Here are some names to stimulate discussion. If there is no discussion, I'll call for a Negative vote. Version strategies of date-time, version-number, state-image version-number is not optional javax.jdo.option.version.DateTime javax.jdo.option.version.StateImage Heterogeneous collections with new-class mapping of subclasses javax.jdo.option.mapping.JoinedTablePerClass (this is tck schema1) javax.jdo.option.mapping.JoinedTablePerConcreteClass (this is tck schema3) javax.jdo.option.mapping.NonJoinedTablePerConcreteClass (this is tck schema2) Mapping fields of Object type and interface types javax.jdo.option.mapping.HeterogeneousObjectType (no tck tests yet) javax.jdo.option.mapping.HeterogeneousInterfaceType (no tck tests yet) Support for the preDirty lifecycle event. javax.jdo.option.PreDirtyEvent (tck tests assume this is true) Craig Russell Architect, Sun Java Enterprise System http://java.sun.com/products/jdo 408 276-5638 mailto:[EMAIL PROTECTED] P.S. A good JDO? O, Gasp! |
smime.p7s
Description: S/MIME cryptographic signature
