Hi, A Dimecres 13 Novembre 2002 23:06, David Graham va escriure: > The developer must make a choice between html and xhtml. This choice is > minor as xhtml is compatible with current browsers. Included jsps should > not be influenced by the includer file; they must decide if they're xhtml > or html. That's the point behind the <html:xhtml> tag, to tell struts > html library tags to render in xhtml. > > If you want to reuse a jsp in an html project then don't code it with xhtml > tags. > > David > >
I don't completely agree with this: "Included jsps should not be influenced by the includer file; they must decide if they're xhtml or html." I think included jsps must not decide a thing that involves the whole request! Anyway I think I can see your point, included jsps should always output the same, xhtml or html, so you can rely on the output of the jsp, even if you are including it from a non-struts jsp page,...... oh well, I think now I completely agree with the above :-) Salut! -- Antoni Reus > > > > > From: Antoni Reus <[EMAIL PROTECTED]> > > >Reply-To: "Struts Developers List" <[EMAIL PROTECTED]> > >To: "Struts Developers List" <[EMAIL PROTECTED]> > >Subject: Re: [VOTE] How to implement XHMTL support > >Date: Wed, 13 Nov 2002 22:53:36 +0100 > > > >Hi, > > > >A Dimecres 13 Novembre 2002 20:45, Martin Cooper va escriure: > > > On Wed, 13 Nov 2002, Eddie Bush wrote: > > > > > > <big-snip/> > > > > > > > If the outermost document is meant to enforce XHTML, how can an > > > >included > > > > > > piece *not* conform to XHTML and the entire document still be XHTML? > > > >I > > > > > > ... feel like we're attempting to over-design - but maybe I'm just > > > > showing my own ignorance (which is something I don't think I'll ever > > > > learn not to do - I learn way too much from being willing to do it). > > > > > > It can't, and that's in part what Craig pointed out. Since each > > > included page must also be XHTML, each of those pages should state > > > explicitly > > > >that > > > > > it is XHTML, instead of having the decision about whether or not to > > > generate XHTML be made externally (i.e. on the topmost page). Given > > > that the non-Struts tags on the page must also be explicitly XHTML, > > > that > > > >makes > > > > > sense. > > > >The document doctype (xhtml1, html401) is global, like the character > >encoding > >or some response headers. There is no sense in changing the doctype flag > > in included pages. > > > >If you develop a page to be included and you use tags other than > >struts-html, > >like <br> or <br /> there is no way to reuse this page in both xhtml and > >html, with or without <html:isXhtml/>, <html:html xhtml="true">, etc .... > >but if a developer is able to create a page to be included that only uses > >struts-html and/or other custom tags, with the <html:isXhtml/> aproach she > >will not be able to reuse its page to generate xhtml or html!!!! > > > > > >Salut! > > > >-- Antoni Reus > > > >-- > >To unsubscribe, e-mail: > ><mailto:struts-dev-unsubscribe@;jakarta.apache.org> > >For additional commands, e-mail: > ><mailto:struts-dev-help@;jakarta.apache.org> > > _________________________________________________________________ > Add photos to your e-mail with MSN 8. Get 2 months FREE*. > http://join.msn.com/?page=features/featuredemail -- To unsubscribe, e-mail: <mailto:struts-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:struts-dev-help@;jakarta.apache.org>
