myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jakob Korherr (JIRA)" <...@myfaces.apache.org>
Subject [jira] [Commented] (MYFACES-3157) Fix order of isRendered and pushComponentToEL invocations
Date Thu, 26 May 2011 15:32:47 GMT

    [ https://issues.apache.org/jira/browse/MYFACES-3157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13039737#comment-13039737
] 

Jakob Korherr commented on MYFACES-3157:
----------------------------------------

we can only do this, if it is not explicitely tested by the TCK!

Unfortunately, TCK-compliance is more important then fixing such spec-bugs...

> Fix order of isRendered and pushComponentToEL invocations
> ---------------------------------------------------------
>
>                 Key: MYFACES-3157
>                 URL: https://issues.apache.org/jira/browse/MYFACES-3157
>             Project: MyFaces Core
>          Issue Type: Bug
>         Environment: myfaces core trunk
>            Reporter: Martin Kočí
>
> Current specification for lifecycles methods:
> 1) processDecodes
> 2) processValidators
> 3) processUpdates
> 4) encodeAll
> 4) encodeBegin
> explicitly says that:
> 1) If the rendered property of this UIComponent is false, skip further processing.
> 2) call pushComponentToEL
> But in that order of invocations it is impossible to achieve rendered like this:
> <h:outputText rendered="#{component.id eq 'outputTextId'}" id="outputTextId" />
> i.e. any rendered ValueEpression based on component itself. In Myfaces  we should implement
in in reverse order, because specified behaviour is buggy.
> Please see this mail thread: http://www.mail-archive.com/dev@myfaces.apache.org/msg53300.html
> and
> http://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-1002
> for details.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message