> -----Original Message----- > From: Norm Deane [mailto:[EMAIL PROTECTED] > Subject: Re: Dynamic Inclusion/Tiles and <f:verabtim> > I've looked at x:div and am using it in some places but the > problem I have with it is that it requires either style or > styleClass. In some cases I don't want either. What I want > sometimes is a div with an id... > <div id="data"> > </div> > Using x:div the best I've been able to come up with is... > <div class="data"> > </div> > Am I missing something?
You can do <x:div class=""/>. Yeah, I consider class/id requirement to be a bug in x:div implementation, but a minor inconvenience at most. It'd be very easy to patch in MyFaces... I guess who is the most bothered about it should should fix it. <x:div> approach is generalizable and already done for the most common html tags. Kalle > Korhonen, Kalle wrote: > > >x:div. > > > >Kalle > > > > > > > >>-----Original Message----- > >>From: Norm Deane [mailto:[EMAIL PROTECTED] > >>Sent: Friday, February 04, 2005 7:21 AM > >>To: MyFaces Discussion > >>Subject: Dynamic Inclusion/Tiles and <f:verabtim> > >> > >>I'm coming from a Struts/Tiles background and really like the Tiles > >>approach to page layout. My first endevour with JSF involves > >>converting an existing Struts/Tiles web application to JSF. > I've got > >>the Tiles integration with MyFaces setup but as I was > converting the > >>tiles (header, footer, body, leftnav, > >>etc) I ran into the JSF requirement that all template text > and custom > >>JSP tags in included pages must be nested in a <f:verbatim> > tag. This > >>led to some really nasty looking pages. For example, I found myself > >>doing this on a couple occasions... > >> > >><f:verbatim><div id="header"></f:verbatim> <h:outputText > >>styleClass="headerText" value="This is my header"/> > >><f:verbatim></div></f:verbatim> > >> > >>Is there another way? How are other people breaking their JSPs down > >>into "modular" chunks so that they can be reused? I guess > one answer > >>is to avoid template text and custom tags all together and just use > >>JSF components exclusively. > >>Unfortunately in this case that is not a realistic option. > >> > >>Thanks, > >> > >>Norm Deane > >>http://jroller.com/page/deanen > >> > >> > >> > >> > >> > > > > > > > >
