Facelets supports c:forEach as well as most of the JSTL c: tags. Same syntax as JSPs, but you're still using Facelets.
-- Adam On 9/18/06, Günther, Thorsten <[EMAIL PROTECTED]> wrote:
Hi Adam! Thanks a lot, but... Now I'm confused. I read that one does not use JSP whith Facelets. Facelets would be pure XHTML and JSF. So I renamed all my Pages to .xhtml and kicked anything out of them that smelled like dirty old JSP. :-) Did I get something wrong here? Regards, Thorsten -----Ursprüngliche Nachricht----- Von: Adam Winer [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 15. September 2006 18:59 An: [email protected] Betreff: Re: ClassCastException In Facelets, you don't use tr:forEach, just c:forEach. Whereas in JSP 2.0 , you can't use c:forEach at all. But in JSP 2.1, back to c:forEach. Simple, huh? ;) -- Adam On 8/29/06, Günther, Thorsten <[EMAIL PROTECTED]> wrote: > > Hi Arnaud! > > Thanks for your suggestion. I remember to have read about tr:forEach and > tr:iterator being rendered at different stages in the page build process. > I'll have to get a deeper understanding of this. > > For me using tr:forEach is not an option since it is not supported by > Facelets. > > Regards, > Thorsten > > > > -----Ursprüngliche Nachricht----- > Von: Arnaud MERGEY [mailto:[EMAIL PROTECTED] > Gesendet: Dienstag, 29. August 2006 08:39 > An: [email protected] > Betreff: Re: ClassCastException > > Hi, > I remember a similar problem, I had a ClassCastException with dynamic > column in table and af:iterator. I think you can only use *tr:forEach* > with trinidad table > try to use *af:forEach* instead of *c:forEach > * > <af:table ...> > <af:forEach var="col" items="#{page.columns}"> > <af:column ...> > </af:forEach> > </af:table> > > Arnaud > > Simon Lessard a écrit : > > Another way would be to add all possible columns to the table and use > > their > > rendered attribute, but depanding on the use case that option might > > not be > > desirable. > > > > On 8/28/06, Simon Lessard <[EMAIL PROTECTED]> wrote: > >> > >> Hello again, > >> > >> I think this case is a good example of the binding attribute usage. You > >> could bind the table to a managed bean and when the getTable() method > >> get > >> called, you add thewanted columns and/or remove the now unwanted ones. > >> > >> > >> Regards, > >> > >> ~ Simon > >> > >> > >> On 8/28/06, Simon Lessard <[EMAIL PROTECTED]> wrote: > >> > > >> > Oh you're right, I read it too fast. Hmm I'll think a bit about > >> that one > >> > and come back with a solution. > >> > > >> > > >> > On 8/28/06, Pablo Saavedra < [EMAIL PROTECTED]> wrote: > >> > > > >> > > I agree this belongs to the user mailing lists, but since we are > >> > > already > >> > > here... > >> > > > >> > > The code you propose would iterate over #{page.columns} but using > >> each > >> > > elements as a row. I think what sebastian wants is to dinamically > >> set > >> > > the > >> > > table's columns (at build time) to later populate it with rows. > >> > > > >> > > I have no idea why the classCast exception is happening, though. > >> > > > >> > > Regards. > >> > > > >> > > 2006/8/28, Simon Lessard < [EMAIL PROTECTED]>: > >> > > > > >> > > > Not sure since I don't use Facelets what often. However, using > >> > > c:foreach > >> > > > with a JSF application is never a good idea unless you're using > >> JSF > >> > > > 1.2.Inyour case I would rather use something like: > >> > > > > >> > > > <af:table value="#{page.columns}" var="col"> > >> > > > <af:column ...> > >> > > > </af:table> > >> > > > > >> > > > > >> > > > Regards, > >> > > > > >> > > > ~ Simon > >> > > > > >> > > > p.s. I think this kind of discussion belong to the user mailing > >> > > list. > >> > > > > >> > > > On 8/28/06, [EMAIL PROTECTED] < > >> > > > [EMAIL PROTECTED] > wrote: > >> > > > > > >> > > > > I have the same Exception if I do something like this: > >> > > > > > >> > > > > <af:table ...> > >> > > > > <c:forEach var="col" items="#{page.columns}"> > >> > > > > <af:column ...> > >> > > > > </c:forEach> > >> > > > > </af:table> > >> > > > > > >> > > > > Any idea? > >> > > > > > >> > > > > Thanks, > >> > > > > Sebastian > >> > > > > > >> > > > > > Hi! > >> > > > > > > >> > > > > > I don't know whether the following is a problem in Trinidad > or > >> > > in > >> > > > > > Facelets, so I start a new topic here, even though this is > >> > > related to > >> > > > my > >> > > > > > other posting "Throw explanatory exception in > >> > > PanelTabbedRenderer for > >> > > > > > wrong typed childs?". > >> > > > > > > >> > > > > > When I try to use a binding="#{someBean.someSetter}" in a > >> > > > tr:panelTabbed > >> > > > > > tag there is not one child returned by component.getChildren > () > >> > > in > >> > > > > > PanelTabbedRenderer but seven. First child is a > >> > > > > > com.sun.facelets.compiler.UIInstructions so we get a > >> > > > ClassCastException. > >> > > > > I > >> > > > > > don't know whether it is ok for Facelets to insert these > >> > > > UIInstructions > >> > > > > > and PanelTabbedRenderer should cope with them or perhaps > >> > > Facelets is > >> > > > > doing > >> > > > > > wrong here. Or maybe I do something real stupid? > >> > > > > > > >> > > > > > Any pointers welcome... > >> > > > > > > >> > > > > > Thanks, > >> > > > > > Thorsten > >> > > > > > > >> > > > > > > >> > > > > > > >> > > > > > 7 child's: > >> > > > > > ------------- > >> > > > > > <tr:panelTabbed position="both" > >> > > > > > binding="#{sammelgruppenDetailView.panelTabbed}" > > >> > > > > > <tr:showDetailItem text="testTab"> > >> > > > > > <tr:outputText > >> > > value="testText"></tr:outputText> > >> > > > > > </tr:showDetailItem> > >> > > > > > </tr:panelTabbed> > >> > > > > > ------------- > >> > > > > > > >> > > > > > > >> > > > > > 1 child: > >> > > > > > ------------- > >> > > > > > <tr:panelTabbed position="both" > > >> > > > > > <tr:showDetailItem text="testTab"> > >> > > > > > <tr:outputText > >> > > value="testText"></tr:outputText> > >> > > > > > </tr:showDetailItem> > >> > > > > > </tr:panelTabbed> > >> > > > > > ------------- > >> > > > > > > >> > > > > > > >> > > > > > >> > > > > > >> > > > > > >> > > > > >> > > > > >> > > > >> > > > >> > > >> > > > > >
