|
This change adds orm.xsd to the jdo implementation, but it has not been tested.
Committed revision 357371. This issue has two parts. The first part is a program that validates xml files according to schema or DTD that is passed in. The program should look for files that have the suffixes .jdo, .orm, and .jdoquery and validate them against both the DTD and schema.
For example, javax.jdo.schema.SchemaTest is the JUnit test that looks for files with the pattern "positiveXXX.jdo, positiveXXX.orm, positiveXXX.jdoquery, negativeXXX.jdo, negativeXXX.orm, negativeXXX.jdoquery" and simply loads them into a standard DOM using a validating parser. All test files named positiveXXX should succeed; tests named negativeXXX should fail to load. The second part is a set of test data that is organized into positive and negative test cases. The union of positive tests should test every feature (each element and attribute) of each of the .orm, .jdo, and .jdoquery schema and DTD. Negative tests will verify for example that no more than one element is permitted if annotated as ? in DTD or maxOccurs=1 in schema. This is just some code to stimulate discussion.
This patch fixes a syntax error in two of the .xsd files, in which the attributes were defined inside the element instead of outside.
The attached patch schemaValidation-060212.patch adds a new test XMLTest.
There is a new patch schemaValidation-060218.patch includes the new test class XMLTest, 6 positive and 2 negative test .jdo files. We still need to add test .orm and .jdoquery files.
Attached you find a new patch schemaValidation-060220.patch for review. It changes the test .jdo files according to the latest jdo.dtd and jdo.xsd updates.
A test program XMLTest has been added to the api20 project.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Committed revision 357371.