Tapestry generates XHTML style output, so it inlcudes a slash before a > on empty tags.
The other issues are problems with your input template. You may need to wrap your <form> with a <p> to make W3C validator happy. You can control the !DOCTYPE of the output document using the Shell component; this may allow you to find a meeting point between what Tapestry generates and what W3C validates. Tapestry si driven by pragmatic concerns; the HTML it outputs works in browsers. On 6/17/05, Koen Segers <[EMAIL PROTECTED]> wrote: > > > > > > Actually this is what tapestry generates: > > > <form method="post" name="Form0" action="/koen/app"> > > > <input type="hidden" name="service" value="direct/1/Login/loginForm"/> > > Switched?! Looks reasonable to me. > > > > My mistake. They aren't switched ... But it still isn't valid. > Any ideas? > I tried a lot of combinations... > This is what W3C states: > > 1. > > Line 29, column 68: document type does not allow element "INPUT" here; > missing one of "P", "H1", "H2", "H3", "H4", "H5", "H6", "PRE", "DIV", > "ADDRESS" start-tag > > ..." name="service" value="direct/1/Login/loginForm"/> > > The mentioned element is not allowed to appear in the context in which > you've placed it; the other mentioned elements are the only ones that are > both allowed there and can contain the element mentioned. This might mean > that you need a containing element, or possibly that you've forgotten to > close a previous element. > > One possible cause for this message is that you have attempted to put a > block-level element (such as "<p>" or "<table>") inside an inline element > (such as "<a>", "<span>", or "<font>"). > > ✉ > 2. > > Line 29, column 69: character data is not allowed here > > ...name="service" value="direct/1/Login/loginForm"/> > > You have used character data somewhere it is not permitted to appear. > Mistakes that can cause this error include putting text directly in the body > of the document without wrapping it in a container element (such as a > <p>aragraph</p>) or forgetting to quote an attribute value (where characters > such as "%" and "/" are common, but cannot appear without surrounding > quotes). > > ✉ > 3. > > Line 30, column 41: document type does not allow element "INPUT" here; > missing one of "P", "H1", "H2", "H3", "H4", "H5", "H6", "PRE", "DIV", > "ADDRESS" start-tag > > <input type="hidden" name="sp" value="S0"/> > > The mentioned element is not allowed to appear in the context in which > you've placed it; the other mentioned elements are the only ones that are > both allowed there and can contain the element mentioned. This might mean > that you need a containing element, or possibly that you've forgotten to > close a previous element. > > One possible cause for this message is that you have attempted to put a > block-level element (such as "<p>" or "<table>") inside an inline element > (such as "<a>", "<span>", or "<font>"). > > ✉ > 4. > > Line 31, column 69: document type does not allow element "INPUT" here; > missing one of "P", "H1", "H2", "H3", "H4", "H5", "H6", "PRE", "DIV", > "ADDRESS" start-tag > > ...name="Form0" value="loginUserName,loginPassword"/> > > The mentioned element is not allowed to appear in the context in which > you've placed it; the other mentioned elements are the only ones that are > both allowed there and can contain the element mentioned. This might mean > that you need a containing element, or possibly that you've forgotten to > close a previous element. > > One possible cause for this message is that you have attempted to put a > block-level element (such as "<p>" or "<table>") inside an inline element > (such as "<a>", "<span>", or "<font>"). > > ✉ > 5. > > Line 35, column 78: there is no attribute "DISPLAYNAME" > > ...e="loginUserName" value="" displayName="Name"/></td> > > You have used the attribute named above in your document, but the > document type you are using does not support that attribute for this element. > This error is often caused by incorrect use of the "Strict" document type > with a document that uses frames (e.g. you must use the "Transitional" > document type to get the "target" attribute), or by using vendor proprietary > extensions such as "marginheight" (this is usually fixed by using CSS to > achieve the desired effect instead). > > This error may also result if the element itself is not supported in the > document type you are using, as an undefined element will have no supported > attributes; in this case, see the element-undefined error message for further > information. > > How to fix: check the spelling and case of the element and attribute, > (Remember XHTML is all lower-case) and/or check that they are both allowed in > the chosen document type, and/or use CSS instead of this attribute. > > -- > > Koen Segers > > <[EMAIL PROTECTED]> > <http://eddyvite.dyndns.org> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator, Jakarta Tapestry Creator, Jakarta HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com
