I fixed the problem by changing:

<!ATTLIST class-descriptor
        class ID #REQUIRED
        isolation-level (read-uncommitted | read-committed | 
repeatable-read |
                         serializable | optimistic | none) ""

in repository.dtd to

<!ATTLIST class-descriptor
        class ID #REQUIRED
        isolation-level (read-uncommitted | read-committed | 
repeatable-read |
                         serializable | optimistic | none) 
"read-uncommitted"

Jon French
Programmer
ECOS Development Team
[EMAIL PROTECTED]
970-226-9290



[EMAIL PROTECTED] 
10/05/2005 02:45 PM
Please respond to
"OJB Users List" <[email protected]>


To

[email protected]
cc





Subject
Repository*.xml validation






I can't get repository*.xml to validate against repository.dtd in either
XMLSpy or MyEclipse.  The most frequent error is "Attribute
'isolation-level' with value '' must have a value from the list 'bla
bla'", even though the .dtd has isolation-level defaulted to
"read-uncommitted", which is in the enumeration, and the .xml has it
defined as isolation-level="read-uncommitted". 

If I take isolation-level out of both the .dtd and the .xml, it
complains about multiple jdbc-connection-descriptors, class-descriptors,
etc.; in other words, anything defined as zero-or-more-occurrences is
acting like it's defined as one-and-only-one-occurrence.  There's dozens
more errors, but I have to think there's something fundamentally wrong
here.

Has anybody else seen anything like this?

Jean

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to