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

Leonardo Uribe commented on MYFACES-2370:
-----------------------------------------

It is obvious that MyFaces has the same bug, because it is a problem in the 
definition of the algorithm of UIData.invokeOnComponent. Note this method 
definition is part of the spec, but theory, if ri change this behavior, we 
could do the same. The only problem is if solve this one makes fail the TCK 
test related to this method, so if we solve this one and some problem happens 
on next release, we could skip this one.

> 'invokeOnComponent' method in UIData does not properly process <h:column> 
> header/footer facets
> ----------------------------------------------------------------------------------------------
>
>                 Key: MYFACES-2370
>                 URL: https://issues.apache.org/jira/browse/MYFACES-2370
>             Project: MyFaces Core
>          Issue Type: Bug
>          Components: General
>    Affects Versions: 1.2.7
>            Reporter: Kennard Consulting
>
> A bug that was originally reported to the RichFaces project here (includes 
> simple test case)...
> https://jira.jboss.org/jira/browse/RF-7700
> ...was identifed by the RichFaces team as being caused by failure to process 
> <h:column> header/footer facets in 'invokeOnComponent'. The RichFaces team 
> reported this to the Mojarra guys...
> https://javaserverfaces.dev.java.net/issues/show_bug.cgi?id=1308
> ...who fixed it in their implementation (as of 1.2_14)
> I then put together a MyFaces version of the same test case (attached as 
> suggestionMyFaces.zip)...
> https://jira.jboss.org/jira/browse/RF-7700
> ...and it appears MyFaces (as of 1.2.7) has the same bug?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to