[ http://jira.jboss.com/jira/browse/JBSEAM-492?page=all ] Gavin King updated JBSEAM-492: ------------------------------ Component/s: Core Fix Version/s: 1.1.0.CR1 Assignee: Stan Silvert -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBSEAM-492?page=all ] Stas Garifulin updated JBSEAM-492: ---------------------------------- Attachment: seam-simple.zip Unless we are talking about EL variables here, it shouldn't matter when the I attached little application which demonstrates the problem i described. After deployment demo page will be accesible at: http://localhost:8080/seam-simple/demo.seam The demo page uses custom facelets tag defined in view/WEB-INF/controls/sample.xhtml. Then you click button on the page you will get NPE in MethodExpressionHelper.findParamTypes. If you will debug this application please put breakpoints in ParamMethodExpression constructor and "invoke" method. Then you will see what ELContexts are different: context in constructor contains mapping info between names used in "sample.xhtml" and actual values passed to control in "demo.xhtml". I already mentioned you can also check facelets sources: they create value expression objects for wrapped expressions during construction too. In my patch i create all neceary EL objects in constructor: target object exression, method expression, arguments exprssions. "ve" variable is used in findParamTypes (i commented 2 lines of code there), you rename it to something like 'targetObjectVe'. Stan -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBSEAM-492?page=comments#action_12347413 ] Stan Silvert commented on JBSEAM-492: ------------------------------------- I have verified that the problem is with resolving EL variables, which we don't yet support in param expressions. I am looking into adding this feature right now. It will be a Facelets-only feature because EL variables are not supported with JSF 1.1/JSP. Unfortunately, I don't think we can use the suggested fix attached to this issue. The problem is that in the suggested fix, findParamTypes() has to resolve part of the expression at construction time by calling ve.getValue(). Because these are deferred expressions, we shouldn't evaluate the values early like that. The targets of the expression might not yet exist. So, I'm going to try to implement this the way Jacob suggested a long time ago when I was trying this out with JSF 1.2. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBSEAM-492?page=all ] Gavin King updated JBSEAM-492: ------------------------------ Fix Version/s: 1.1.0.GA (was: 1.1.0.CR1) Priority: Major (was: Blocker) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBSEAM-492?page=all ] Gavin King updated JBSEAM-492: ------------------------------ Fix Version/s: (was: 1.1.1.GA) Deprioritizing this, better to wait for jboss-el. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira