It is my hope that someone with Slide checkin permissions will adopt Domain.xsd. As to the url I used, if it should be "http://jakarta.apache.org/slide"; and not "xmlns="http://www.apache.org/slide";, thats something that the jakarta folks should decide - I don't really care, but I would assume that apache and/or jakarta might have some standard xml schema namespace rules but I do not know what they are.
Richard
Martin Holz wrote:
Thank you. This can save a lot of debugging.
Richard Emberson <[EMAIL PROTECTED]> writes:
Included is an attempt at formalizing the definition of a Domain.xml file - a Domain.xsd file. To use it one has to add the following attribute to your Domain.xml 'slide' element:
xmlns="http://www.apache.org/slide";
Any reason you used this url and not http://jakarta.apache.org/slide ?
I used msv for validation of my Domain.xml and found a few problems:
1) Error at line:31, column:85 of file:///home/holz/HEAD/src/slide/conf/slide.xconf attribute "classname" has a bad value: the value does not match the regular expression "[a-zA-Z]\w*(\.[a-zA-Z]\w*)*".
Line 31 looks like this: <nodestore classname="de.vs_c.slide.store.PostgresDescriptorsStore">
http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/#nt-MultiCharEsc is not very readable, but I
guess \w does not match the underscore. \c seems to fit better.
2) The schema expects a <parameter> element inside <content-interceptor>. However parameter are optional.
3) Error at line:58, column:33 of file:///home/holz/HEAD/src/slide/conf/slide.xconf tag name "store" is not allowed. Possible tag names are: <scope>
I use something like <store name="jdbc" >...</store>
<scope match="/" store="jdbc" />
<store name="ldap" >...</store> <scope match="/users" store="ldap" />
while the schema expects <store name="jdbc" >...</store>
<store name="ldap" >...</store>
<scope match="/" store="jdbc" /> <scope match="/users" store="ldap" />
Maybe I should reorganize my Domain.xml here.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
