This one time, at band camp, David Nemeshazy said:
DN>I want to use the HIGH/LOW key generator with Castor and turn the validation
DN>on. The version of Castor I am using is 0.9.4.
DN>
DN>There are two problems with the current mapping schema or DTD when
DN>validation is on :
DN>- In the class element, the attribute key-generator is defined as NMTOKEN in
DN>the DTD, but "HIGH/LOW" is not a NMTOKEN (with validation on, I get the
DN>following error : Parsing Error : Attribute value "HIGH/LOW" of type NMTOKEN
DN>must be a name token). Ok, this can be corrected using an alias, but then
DN>the next problem appears.
DN>- In the key-generator element, the name attribute is defined as ID in the
DN>DTD, as xsd:ID in the schema, and here again, "HIGH/LOW" is not a valid ID
DN>(with validation on, I get the following error : Parsing Error : Attribute
DN>value "HIGH/LOW" of type ID must be a name)
DN>
DN>I have opened a new bug (#1086) for this. In my opinion, the best option is
DN>to rename HIGH/LOW to something else, HIGH-LOW for example, which is correct
DN>according to the DTD and schema.
DN>
DN>By the way, wouldn't it be a good idea to run test cases with validation
DN>turned on?
David,
I don't see a problem with chaging the name of the HIGH/LOW key generator
to HIGH-LOW. Thanks for taking the time to the file the bug.
Bruce
--
perl -e 'print unpack("u30","<0G)U8V4\@4VYY9&5R\"F9E<G)E=\$\!F<FEI+F-O;0\`\`");'
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
