Re: JSTL-Faces bridge broken?

[Werner Punz <we...@gmx.at>]

There are several cases where you can mix and match both.
c:if is one of them. c:foreach is not.
but as I said the problem was an old jar which broke things left and  
right.
c:if is in most cases unecessary, I replaced my c:if with a rendered  
attribute
does the same and does not have to rely on jstl



Am 20.04.2005 um 16:59 schrieb Sean Schofield:

> There are known issues with JSTL and JSF but I am not an expert enough
> at either to say for sure this is your problem.  I take it you are
> aware that you are not really supposed to be mixing the two right?
> The new JSF spec seems to make big strides in that area however.
>

Re: JSTL-Faces bridge broken?

[Craig McClanahan <cr...@gmail.com>]

On 5/4/05, Rob Decker <ro...@objectsource.org> wrote:
>  
> The <c:if> tag and rendered attribute are actually slightly different. 
>   
> This prevents the component from being added to the heirachy: 
>   
> <c:if test="${false}"> 
>     <h:outputText value="hello"/>
> </c:if> 
>   
> This prevents the component from being rendered but it still exists in the
> heirarchy: 
>   
> <h:outputText value="hello" rendered="false"/> 
>   
> I've found <c:if> can be useful because it does that.
>  

One cautionary note -- if you use <c:if> in this manner, components
enclosed within it should ALWAYS have an "id" value.  This avoids
problems when ids are being automatically assigned, you redisplay the
same page, and the IF condition has chaged since when the page was
originally rendered (thus, the component that was omitted before is
now included, or vice versa).

Craig

Re: JSTL-Faces bridge broken?

[Rob Decker <ro...@objectsource.org>]

The <c:if> tag and rendered attribute are actually slightly different.

This prevents the component from being added to the heirachy:

<c:if test="${false}">
    <h:outputText value="hello"/>
</c:if>

This prevents the component from being rendered but it still exists in the heirarchy:

<h:outputText value="hello" rendered="false"/>

I've found <c:if> can be useful because it does that.

----- Original Message ----- 
  From: Werner Punz 
  To: MyFaces Discussion 
  Sent: Tuesday, May 03, 2005 1:47 PM
  Subject: Re: JSTL-Faces bridge broken?


  There are several cases where you can mix and match both.
  c:if is one of them. c:foreach is not.
  but as I said the problem was an old jar which broke things left and right.
  c:if is in most cases unecessary, I replaced my c:if with a rendered attribute
  does the same and does not have to rely on jstl






  Am 20.04.2005 um 16:59 schrieb Sean Schofield:


    There are known issues with JSTL and JSF but I am not an expert enough

    at either to say for sure this is your problem.  I take it you are

    aware that you are not really supposed to be mixing the two right? 

    The new JSF spec seems to make big strides in that area however.