On Tue, 22 Oct 2002, David Graham wrote:
> Date: Tue, 22 Oct 2002 21:37:42 -0600 > From: David Graham <[EMAIL PROTECTED]> > Reply-To: Struts Developers List <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: Re: HTML, XML, XHTML and <html:html> > > Well I've been wrong before and I'm obviously wrong now :-). Thanks for the > links. I saw in a different part of the xhtml docs something about boolean > attributes being true and false. Who in their right mind designs a system > where "boolean" attributes can only take their name as the value? That > doesn't make any sense. > Welcome to the wonderful world of standards bodies :-). The compromises that are necessary sometimes can be quite amazing ... > Regardless, given the statement that xhtml 2.0 will not be html compatible > maybe there should be an xhtml taglib. I like the idea of having the xhtml > taglib being the html taglib with the xhtml setting defaulted to true. That > way, we can easily implement xhtml 1.0. <soapbox> Meant to comment on the XHTML 1.0 versus 1.1 versus 2.0 thing ... thanks for reminding me. At this point, XHTML 2.0 is nothing more than the gleam in some working group's eye (well, they're at "Working Draft" state in the W3C process, which is kind sorta like an alpha). I'm not at all interested in caring about it until it reaches Recommended status -- and even then, I'm only interested if the world starts to care about it. Making standards that are substantially non-backwards compatible is not, IMHO, a good way to gain popularity -- but the W3C is full of working groups that don't seem overly concerned about this. The next year or so is going to be quite interesting. </soapbox> > Will JavaServer Faces handle xhtml? Remember that there are two levels to JavaServer Faces * An API framework on which you can build a RenderKit that outputs any sort of text or binary markup that you like (including XHTML). * An out-of-the box implementation of a RenderKit for HTML/4.01, to make it possible to use JavaServer Faces immediately. > Should we even bother with doing this in Struts? I can tell you that *I'm* not going to worry too much about the existing Struts tag libraries (other than bugfixes etc.) once JSF goes final. I think there will be ample room for innovation in creating JSF-compatible components -- both those that are Struts specific (such as a Struts version of the standard JSF UIForm component, which adds the usual action lookup and form bean processing of <html:form>), and components+renderers that are not specific to Struts. Doing an XHTML based RenderKit based on JSF components sounds like a much more useful long-term thing than doing this to the struts-html tags. Other committers, of course, may have different ideas -- and that is fine as well. The alternatives are not mutually exclusive. > > Dave Craig -- To unsubscribe, e-mail: <mailto:struts-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:struts-dev-help@;jakarta.apache.org>
