[Jdo Wiki] Update of Chapter18TestComponents by MichelleCaisse
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 MichelleCaisse: http://wiki.apache.org/jdo/Chapter18TestComponents -- || !ELEMENT join (column*, index?, foreign-key?, extension*) ||CompletenessTest||Company||default||.|| || !ATTLIST join table CDATA #IMPLIED ||CompletenessTest||Company||default||.|| || !ATTLIST join column CDATA #IMPLIED ||CompletenessTest||Company||default||.|| - || !ATTLIST join outer (true|false) ?false? ||n ||Company ||default||.|| + || !ATTLIST join outer (true|false) ?false? ||++||Company||default||.|| || !ATTLIST join foreign-key CDATA #IMPLIED ||CompletenessTest||Company||default||.|| || !ELEMENT datastore-identity ((column)*, (extension)*) ||CompletenessTest||Company||default||.|| || !ATTLIST datastore-identity column CDATA #IMPLIED ||CompletenessTest||Company||default||.|| || !ATTLIST datastore-identity strategy CDATA #IMPLIED ||CompletenessTest||Company||multiple mappings||.|| - || !ATTLIST datastore-identity sequence-name CDATA #IMPLIED ||n ||Company||multiple mappings||.|| + || !ATTLIST datastore-identity sequence-name CDATA #IMPLIED ||++||Company||multiple mappings||.|| - || !ATTLIST datastore-identity factory-class CDATA #IMPLIED ||n ||Company||multiple mappings||.|| + || !ATTLIST datastore-identity factory-class CDATA #IMPLIED ||++||Company||multiple mappings||.|| || !ELEMENT implements ((property-field)+, (extension)*) ||InterfaceTest||Interface model||interface mapping||.|| || !ATTLIST implements name CDATA #REQUIRED ||InterfaceTest||Interface model||interface mapping||.|| || !ELEMENT inheritance (discriminator?, extension*) ||CompletenessTest||Company||.||.|| @@ -43, +43 @@ || !ELEMENT column (extension*) ||CompletenessTest||Company||default||.|| || !ATTLIST column name CDATA #IMPLIED ||CompletenessTest||Company||default||.|| || !ATTLIST column target CDATA #IMPLIED ||CompletenessTest||Company||default||.|| - || !ATTLIST column target-field CDATA #IMPLIED ||n ||special test xcalia ||.||.|| + || !ATTLIST column target-field CDATA #IMPLIED ||++||special test xcalia ||.||.|| || !ATTLIST column jdbc-type CDATA #IMPLIED ||CompletenessTest||Company||default||.|| - || !ATTLIST column sql-type CDATA #IMPLIED ||n ||special mapping ||.||.|| + || !ATTLIST column sql-type CDATA #IMPLIED ||++||special mapping ||.||.|| || !ATTLIST column length CDATA #IMPLIED ||CompletenessTest||Company||default||.|| || !ATTLIST column scale CDATA #IMPLIED ||CompletenessTest||Company||default||.|| || !ATTLIST column nulls-allowed CDATA #IMPLIED ||CompletenessTest ||Company||default||.|| @@ -57, +57 @@ || !ATTLIST field persistence-modifier (persistent|transactional|none) #IMPLIED ||CompletenessTest ||Company||default||.|| || !ATTLIST field table CDATA #IMPLIED ||CompletenessTest||Company||default||.|| || !ATTLIST field null-value (exception|default|none) ?none? ||CompletenessTest||Company||different mapping||.|| - || !ATTLIST field default-fetch-group (true|false) #IMPLIED ||CompletenessTest||different test case, different mappings ||.||.|| + || !ATTLIST field default-fetch-group (true|false) #IMPLIED ||different test||Company||different mappings||.|| || !ATTLIST field embedded (true|false) #IMPLIED ||CompletenessTest||Company||different mappings||.|| - || !ATTLIST field serialized (true|false) #IMPLIED ||n ||different mappings ||.||.|| + || !ATTLIST field serialized (true|false) #IMPLIED ||CompletenessTest||Company||different mappings||.|| - || !ATTLIST field dependent (true|false) #IMPLIED ||CompletenessTest ||y||default||.|| + || !ATTLIST field dependent (true|false) #IMPLIED ||CompletenessTest||Company||default||.|| - || !ATTLIST field value-factory CDATA #IMPLIED ||n ||different test case different mapping ||.||.|| + || !ATTLIST field value-factory CDATA #IMPLIED ||different test||special model||special mapping||8|| - || !ATTLIST field foreign-key CDATA #IMPLIED ||CompletenessTest ||y||default||.|| + || !ATTLIST field foreign-key CDATA #IMPLIED ||CompletenessTest||Company||default||.|| - || !ATTLIST field fetch-group CDATA #IMPLIED ||n ||same test different mapping ||.||.|| + || !ATTLIST field fetch-group CDATA #IMPLIED ||CompletenessTest||Company||different mapping||.|| || !ATTLIST field depth CDATA #IMPLIED ||n ||different test case ||.||.|| - || !ELEMENT foreign-key (column*, extension*) ||CompletenessTest ||. ||.||.|| + || !ELEMENT foreign-key (column*, extension*) ||CompletenessTest ||Company||default||.|| - || !ATTLIST foreign-key deferred (true|false) #IMPLIED ||n ||different test case different mapping ||.||.|| + || !ATTLIST foreign-key deferred (true|false) #IMPLIED ||different test case||Company||different mapping||8|| - || !ATTLIST foreign-key delete-action (cascade|restrict|null|default) #IMPLIED ||n ||what does this mean?
[Jdo Wiki] Update of Chapter18TestComponents by MichelleCaisse
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 MichelleCaisse: http://wiki.apache.org/jdo/Chapter18TestComponents New page: = XML Metadata Test Coverage = The standard mappings of Company model will use the following elements and attributes. ||XML Element/attribute||Test||Model||Mapping||Priority|| || !ELEMENT jdo ((package)+, (query)*, (extension)*) ||CompletenessTest||Company||default||.|| || !ELEMENT package (interface*, class*, sequence*, extension*) ||CompletenessTest||Company||default||.|| || !ATTLIST package name CDATA #REQUIRED ||CompletenessTest||Company||default||.|| || !ELEMENT interface ((property)*, (extension*)) ||InterfaceTest||Interface model||interface mapping||.|| || !ATTLIST interface name CDATA #REQUIRED ||InterfaceTest||Interface model||interface mapping||.|| || !ATTLIST interface requires-extent (true|false) ?true? ||InterfaceTest||Interface model||interface mapping||.|| || !ELEMENT property ((collection|map|array|column)? , extension*)||InterfaceTest||Interface model||interface mapping||.|| || !ATTLIST property name CDATA #REQUIRED ||InterfaceTest||Interface model||interface mapping||.|| || !ATTLIST property column CDATA #IMPLIED ||InterfaceTest||Interface model||interface mapping||.|| || !ELEMENT class (datastore-identity?, implements*, inheritance?, join*, foreign-key*, index*, field*, version?, query*, fetch-group*, extension*) ||CompletenessTest||Company||default||.|| || !ATTLIST class name CDATA #REQUIRED ||CompletenessTest||Company||default||.|| || !ATTLIST class identity-type (application|datastore|nondurable) #IMPLIED ||CompletenessTest||Company||default||.|| || !ATTLIST class table CDATA #IMPLIED ||CompletenessTest||Company||default||.|| || !ATTLIST class requires-extent (true|false) ?true? ||CompletenessTest||Company||default||.|| || !ATTLIST class persistence-capable-superclass CDATA #IMPLIED ||n/a ||. ||.||.|| || !ATTLIST class embedded-only (true|false) #IMPLIED ||CompletenessTest||Company ||default||.|| || !ATTLIST class persistence-modifier (persistence-capable|persistence-aware|non-persistent) #IMPLIED ||CompletenessTest||Company||.||.|| || !ELEMENT join (column*, index?, foreign-key?, extension*) ||CompletenessTest||Company||default||.|| || !ATTLIST join table CDATA #IMPLIED ||CompletenessTest||Company||default||.|| || !ATTLIST join column CDATA #IMPLIED ||CompletenessTest||Company||default||.|| || !ATTLIST join outer (true|false) ?false? ||n ||Company ||default||.|| || !ATTLIST join foreign-key CDATA #IMPLIED ||CompletenessTest||Company||default||.|| || !ELEMENT datastore-identity ((column)*, (extension)*) ||CompletenessTest||Company||default||.|| || !ATTLIST datastore-identity column CDATA #IMPLIED ||CompletenessTest||Company||default||.|| || !ATTLIST datastore-identity strategy CDATA #IMPLIED ||CompletenessTest||Company||multiple mappings||.|| || !ATTLIST datastore-identity sequence-name CDATA #IMPLIED ||n ||Company||multiple mappings||.|| || !ATTLIST datastore-identity factory-class CDATA #IMPLIED ||n ||Company||multiple mappings||.|| || !ELEMENT implements ((property-field)+, (extension)*) ||separate schema ||.||.||.|| || !ATTLIST implements name CDATA #REQUIRED ||separate schema ||.||.||.|| || !ELEMENT inheritance (discriminator?, extension*) ||CompletenessTest||Company||.||.|| || !ATTLIST inheritance strategy CDATA #IMPLIED ||CompletenessTest||Company||multiple mappings||.|| || !ELEMENT discriminator (column?, extension*) ||CompletenessTest||Company||.||.|| || !ATTLIST discriminator column CDATA #IMPLIED ||CompletenessTest||Company||multiple||.|| || !ATTLIST discriminator value CDATA #IMPLIED ||CompletenessTest||Company||multiple||.|| || !ATTLIST discriminator strategy CDATA #IMPLIED ||CompletenessTest ||Company||multiple||.|| || !ELEMENT column (extension*) ||CompletenessTest||Company||default||.|| || !ATTLIST column name CDATA #IMPLIED ||CompletenessTest||Company||default||.|| || !ATTLIST column target CDATA #IMPLIED ||CompletenessTest||Company||default||.|| || !ATTLIST column target-field CDATA #IMPLIED ||n ||special test xcalia ||.||.|| || !ATTLIST column jdbc-type CDATA #IMPLIED ||CompletenessTest||Company||default||.|| || !ATTLIST column sql-type CDATA #IMPLIED ||n ||special mapping ||.||.|| || !ATTLIST column length CDATA #IMPLIED ||CompletenessTest||Company||default||.|| || !ATTLIST column scale CDATA #IMPLIED ||CompletenessTest||Company||default||.|| || !ATTLIST column nulls-allowed CDATA #IMPLIED ||CompletenessTest ||Company||default||.|| || !ELEMENT property-field (extension*) ||InterfaceTest||Interface model||interface mapping||.|| || !ATTLIST property-field name #REQUIRED ||InterfaceTest||Interface model||interface mapping||.|| || !ATTLIST property-field field-name #REQUIRED ||InterfaceTest||Interface model||interface mapping||.|| || !ELEMENT field ((collection|map|array|(column*))?, join?, element?,
[Jdo Wiki] Update of Chapter18TestComponents by MichelleCaisse
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 MichelleCaisse: http://wiki.apache.org/jdo/Chapter18TestComponents -- || !ATTLIST datastore-identity strategy CDATA #IMPLIED ||CompletenessTest||Company||multiple mappings||.|| || !ATTLIST datastore-identity sequence-name CDATA #IMPLIED ||n ||Company||multiple mappings||.|| || !ATTLIST datastore-identity factory-class CDATA #IMPLIED ||n ||Company||multiple mappings||.|| - || !ELEMENT implements ((property-field)+, (extension)*) ||separate schema ||.||.||.|| - || !ATTLIST implements name CDATA #REQUIRED ||separate schema ||.||.||.|| + || !ELEMENT implements ((property-field)+, (extension)*) ||InterfaceTest||Interface model||interface mapping||.|| + || !ATTLIST implements name CDATA #REQUIRED ||InterfaceTest||Interface model||interface mapping||.|| || !ELEMENT inheritance (discriminator?, extension*) ||CompletenessTest||Company||.||.|| || !ATTLIST inheritance strategy CDATA #IMPLIED ||CompletenessTest||Company||multiple mappings||.|| || !ELEMENT discriminator (column?, extension*) ||CompletenessTest||Company||.||.||
[Jdo Wiki] Trivial Update of XmlSchema by BrianTopping
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 BrianTopping: http://wiki.apache.org/jdo/XmlSchema -- This makes the most sense to me. Schema is not exceptionally more difficult to read than DTD, and tools support for it is widespread now. DTD is not easily digestable by XML toolsets for metadata transformations. This is especially important in MDA applications. - = Option 2: Normative XML Schema, non-normative DT D= + = Option 2: Normative XML Schema, non-normative DTD = If we go this route, I believe that the DTD should be generated from the Schema. This is unfortunately difficult because Schema contains a couple of constructions that cannot be translated. Manual synchronization of the DTD to Schema is going to be prone to error, if it occurs at all.
[Jdo Wiki] Update of XmlSchema by BrianTopping
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 BrianTopping: http://wiki.apache.org/jdo/XmlSchema New page: There was a discussion on the email list about what the plan was here, but I'm blonde, and it's not entirely obvious what the conclusion was. =Option 1: No DTD, only normative Schema= This makes the most sense to me. Schema is not exceptionally more difficult to read than DTD, and tools support for it is widespread now. DTD is not easily digestable by XML toolsets for metadata transformations. This is especially important in MDA applications. =Option 2: Normative XML Schema, non-normative DTD= If we go this route, I believe that the DTD should be generated from the Schema. This is unfortunately difficult because Schema contains a couple of constructions that cannot be translated. Manual synchronization of the DTD to Schema is going to be prone to error, if it occurs at all. =Option 3: DTD only= I think this has already been eliminated. Comments?
[Jdo Wiki] Update of XmlSchema by BrianTopping
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 BrianTopping: http://wiki.apache.org/jdo/XmlSchema -- There was a discussion on the email list about what the plan was here, but I'm blonde, and it's not entirely obvious what the conclusion was. - =Option 1: No DTD, only normative Schema= + = Option 1: No DTD, only normative Schema = This makes the most sense to me. Schema is not exceptionally more difficult to read than DTD, and tools support for it is widespread now. DTD is not easily digestable by XML toolsets for metadata transformations. This is especially important in MDA applications. - =Option 2: Normative XML Schema, non-normative DTD= + = Option 2: Normative XML Schema, non-normative DT D= If we go this route, I believe that the DTD should be generated from the Schema. This is unfortunately difficult because Schema contains a couple of constructions that cannot be translated. Manual synchronization of the DTD to Schema is going to be prone to error, if it occurs at all. - =Option 3: DTD only= + = Option 3: DTD only = I think this has already been eliminated.
[Jdo Wiki] Update of FrontPage by BrianTopping
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 BrianTopping: http://wiki.apache.org/jdo/FrontPage -- * The objective of JDO is to support J2SE 1.3 for runtime. You find details about running with J2SE 1.3 at the [J2SESupport] page. + * A DeveloperScratchpad is available for uncategorized issues. + = Downloads = Until svn is setup, tarballs of snapshots are available at SubversionRepository
[Jdo Wiki] Update of DeveloperScratchpad by BrianTopping
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 BrianTopping: http://wiki.apache.org/jdo/DeveloperScratchpad New page: * DevelopmentMethodology considers whether project momentum and organization might be aided by adopting a process such as XP. * ReleaseNomenclature describes the meaning of version and release cycle names.
[Jdo Wiki] Update of DeveloperScratchpad by BrianTopping
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 BrianTopping: http://wiki.apache.org/jdo/DeveloperScratchpad -- * DevelopmentMethodology considers whether project momentum and organization might be aided by adopting a process such as XP. + * ReleaseNomenclature describes the meaning of version and release cycle names.
[Jdo Wiki] Update of DevelopmentMethodology by BrianTopping
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 BrianTopping: http://wiki.apache.org/jdo/DevelopmentMethodology New page: ''This document considers whether a development process such as eXtreme Programming might help us meet our goals more successfully than our current process. '' No matter how you choose to label it, all projects have a development process. Projects that document their development process often find themselves to be more successful because particpants can help themselves when need arises. Every project has different goals and team members, so no one process fits all projects. If you haven't read much about eXtreme Programming, I would encourage you to consider whether this could work for us, minus the cheerleading and rigor. We aren't a centralized crew (I always see rainbows when I think of team programming anyway), we don't have a traditional customer (although we might do well to define one), so many of the components of their process should not be taken at face value. If we were just to focus on the development cycle and their use of task cards and frequent releases, we might collectively find that we make more organized and focused progres. There is a very good program called [http://www.xplanner.org XPlanner] that would work very well for organizing thoughts and tasks for a distributed team. I'm not sure if Apache infrastructure can support J2EE deployments yet though. If not, I would be happy to host it.
[Jdo Wiki] Update of Chapter18TestCoverageNotes by MichelleCaisse
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 MichelleCaisse: http://wiki.apache.org/jdo/Chapter18TestCoverageNotes -- || !ATTLIST extension key CDATA #IMPLIED ||n/a ||. || || !ATTLIST extension value CDATA #IMPLIED ||n/a ||. || + + Next rev draft at Chapter18TestComponents. +
[Jdo Wiki] Update of FrontPage by MichelleCaisse
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 MichelleCaisse: http://wiki.apache.org/jdo/FrontPage -- * There are a number of items on the ToDoList. You can volunteer for any of them... - * The subversion repository is being set up. You can take a look at the SubversionRepository page for more information. + * The subversion repository has been set up. You can take a look at the SubversionRepository page for more information. * The apache JDO project uses maven for build. You can take a look at the MavenInfo page for more information.
[Jdo Wiki] Update of SubversionRepository by MichelleCaisse
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 MichelleCaisse: http://wiki.apache.org/jdo/SubversionRepository -- = Overview = - Apache JDO uses [http://subversion.tigris.org Subversion] to manage its source code. Instructions on Subversion use can be found here [http://svnbook.red-bean.com here]. + Apache JDO uses [http://subversion.tigris.org Subversion] to manage its source code. Instructions on Subversion use can be found here [http://svnbook.red-bean.com here]. To receive notice of commits to the repository subscribe to [EMAIL PROTECTED] by sending email to [EMAIL PROTECTED] '''Current version'''
[Jdo Wiki] Update of ToDoList by MichelleCaisse
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 MichelleCaisse: http://wiki.apache.org/jdo/ToDoList -- ||Project||Activity wiki page||Description||Who||Expected Completion Date|| ||JDO TCK 2.0 ||DataBaseGen||Database Generator. This program takes .orm, .jdo, and .class files and generates DDL.||jpox||done?|| ||FOStore 1.1, 2.0 ||NewTypeSupport||New types added in JDK 1.4 [http://java.sun.com/j2se/1.5.0/docs/api/java/util/Currency.html Currency], [http://java.sun.com/j2se/1.5.0/docs/api/java/util/LinkedHashSet.html LinkedHashSet], [http://java.sun.com/j2se/1.5.0/docs/api/java/util/LinkedHashMap.html LinkedHashMap] need to be supported as persistent field types. This is optional for JDO 1.1, but required for JDO 2.0.||tbd||tbd|| - ||JDO TCK 2.0||TestRunner||Modify the JUnit test runner program so that the same TCK tests can be run in multiple configurations. For example, the same TCK test program needs to be run with and without security turned on, and with Application Identity and Datastore Identity. When we add different mappings for Chapter 18 (ORM) tests, the same test will need to be run with security, identity, and different mappings.||tbd||tbd|| + ||JDO TCK 2.0||TechnologyCompatibilityKit||Tasks listed on the ToDo list on the TCK page||various||tbd|| - ||jdo2.jar||Jdo2Jar||Create a jar file for the JDO 2 api||Craig Russell||tbd|| + ||jdo2.jar||Jdo2Jar||Create a jar file for the JDO 2 api||Craig Russell||done|| ||XML Schema||XmlSchema||Create an xml schema corresponding to the JDO 2 draft dtd's||Brian Topping||tbd|| -
[Jdo Wiki] Update of TechnologyCompatibilityKit by MichelleCaisse
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 MichelleCaisse: http://wiki.apache.org/jdo/TechnologyCompatibilityKit -- = TCK ToDo = This is the list of tasks required to complete the JDO 2.0 TCK. ||Activity wiki page||Description||Who||Expected Completion Date|| - ||TestRunner||Extend test runners to allow test parameterization||Michael Bouschen||?/05|| + ||TestRunner||Modify the JUnit test runner program so that the same TCK tests can be run in multiple configurations. For example, the same TCK test program needs to be run with and without security turned on, and with Application Identity and Datastore Identity. When we add different mappings for Chapter 18 (ORM) tests, the same test will need to be run with security, identity, and different mappings.||Michael Bouschen||?/05|| ||[XMLMetadata]||Develop xml metadata tests (Chapter 18)||Michelle Caisse others TBD||?/05|| ||QueryTests11||Finish JDO 1 TCK query test classes||Michael Bouschen||done March 05|| ||QueryTests||Write tests for the query language enhancements and new query api's||Michael Bouschen||?/05||
[Jdo Wiki] Update of SubversionRepository by MichelleCaisse
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 MichelleCaisse: http://wiki.apache.org/jdo/SubversionRepository -- Apache JDO uses [http://subversion.tigris.org Subversion] to manage its source code. Instructions on Subversion use can be found here [http://svnbook.red-bean.com here]. - Until the repository is set up, this page will contain the latest working copy of the Apache JDO code. + '''Current version''' - '''Current version''' + The Apache subversion repository contains the latest code. + + '''Previous versions''' Download the 2005-03-08 version [attachment:apache-jdo-2005-03-08.zip here]. It implements the remaining JDO TCK 1 query test cases. The subproject structure has been changed by adding directories java, dtd, jdo, etc. under src and test. The tck11 subproject uses some basic test configuration as described in TestRunner. - - '''Previous versions''' Download the 2005-02-17 version [attachment:apache-jdo-2005-02-17.zip here]. It fixes a problem with running the ri11/tck11 subprojects under windows.
