[
https://issues.apache.org/jira/browse/MYFACES-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13192593#comment-13192593
]
Kennard Consulting commented on MYFACES-3410:
---------------------------------------------
This appears to have been fixed somewhere along the line. It is broken in
Tomcat 7.0.21, but fixed in Tomcat 7.0.25.
Would it be worth figuring out how this happened? It's not JSF (I used MyFaces
2.1.4 both times) or el-api.jar (both Tomcats use 2.2.FR), so I guess it must
be in the EL implementation somewhere?
Could you help get some regression tests around this?
> Method parameters only work on 'top-level' managed beans
> --------------------------------------------------------
>
> Key: MYFACES-3410
> URL: https://issues.apache.org/jira/browse/MYFACES-3410
> Project: MyFaces Core
> Issue Type: Bug
> Environment: MyFaces 2.1.4, Tomcat 7.0.21 (also tried JBoss AS 7)
> Reporter: Kennard Consulting
> Attachments: ELParamsTest.zip
>
>
> When using JSF 2's 'method parameters' feature:
> #{fooBean.add(42)}
> The evaluation fails when trying on a child object:
> #{fooBean.foo.add(42)}
> As a workaround you can use:
> <ui:param name="_foo" value="#{fooBean.foo}"/>
> #{_foo.add(42)}
> But this seems like it should work without needing ui:param?
> See attached test case.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
