[jira] [Commented] (MYFACES-3542) The render attribute of AjaxBehavior should support late value expression evaluation
[ https://issues.apache.org/jira/browse/MYFACES-3542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13777657#comment-13777657 ] Dora Rajappan commented on MYFACES-3542: This particular behaviour of evaluating the render ids on the fly and then rendering those ids is not something the spec thought of implementing. The render attribute of AjaxBehavior should support late value expression evaluation Key: MYFACES-3542 URL: https://issues.apache.org/jira/browse/MYFACES-3542 Project: MyFaces Core Issue Type: New Feature Reporter: Bernd Bohmann Attachments: late-render-expression-0.png, late-render-expression-1.png, late-render-expression-2.png, late-render-expression-3.png, late-render-expression-4.png, late-render-expression.tgz The render attribute of AjaxBehavior should evaluated during post-back after 'Invoke Application' and before 'Render Response'. It's easly to add this feature with a own PartialViewContext. But there is no call to processPartial with 'Invoke Application'. The Phase 'Render Response' is too late if you are using c:if to skip components from the component tree. See attached example app and pictures. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MYFACES-3542) The render attribute of AjaxBehavior should support late value expression evaluation
[ https://issues.apache.org/jira/browse/MYFACES-3542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13777676#comment-13777676 ] Dora Rajappan commented on MYFACES-3542: There is no problem with c:if component behaviour with visit algorithm also. Info2 component is in execute and when the checkbox was deselected subsequent ajax request test2 got skipped which is expected. If info2 is removed from execute ajax render wont skip test2 . Preference is clearly for ajax. I misunderstood the problem was with skipping components and not purely for late value expression evaluation for render attribute. The render attribute of AjaxBehavior should support late value expression evaluation Key: MYFACES-3542 URL: https://issues.apache.org/jira/browse/MYFACES-3542 Project: MyFaces Core Issue Type: New Feature Reporter: Bernd Bohmann Attachments: late-render-expression-0.png, late-render-expression-1.png, late-render-expression-2.png, late-render-expression-3.png, late-render-expression-4.png, late-render-expression.tgz The render attribute of AjaxBehavior should evaluated during post-back after 'Invoke Application' and before 'Render Response'. It's easly to add this feature with a own PartialViewContext. But there is no call to processPartial with 'Invoke Application'. The Phase 'Render Response' is too late if you are using c:if to skip components from the component tree. See attached example app and pictures. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MYFACES-3542) The render attribute of AjaxBehavior should support late value expression evaluation
[ https://issues.apache.org/jira/browse/MYFACES-3542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13776344#comment-13776344 ] Dora Rajappan commented on MYFACES-3542: The spec has given preference to c:if over ajax and can be corrected otherwise it will defeat the purpose of ajax. The render attribute of AjaxBehavior should support late value expression evaluation Key: MYFACES-3542 URL: https://issues.apache.org/jira/browse/MYFACES-3542 Project: MyFaces Core Issue Type: New Feature Reporter: Bernd Bohmann Attachments: late-render-expression-0.png, late-render-expression-1.png, late-render-expression-2.png, late-render-expression-3.png, late-render-expression-4.png, late-render-expression.tgz The render attribute of AjaxBehavior should evaluated during post-back after 'Invoke Application' and before 'Render Response'. It's easly to add this feature with a own PartialViewContext. But there is no call to processPartial with 'Invoke Application'. The Phase 'Render Response' is too late if you are using c:if to skip components from the component tree. See attached example app and pictures. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MYFACES-3542) The render attribute of AjaxBehavior should support late value expression evaluation
[ https://issues.apache.org/jira/browse/MYFACES-3542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13776377#comment-13776377 ] Dora Rajappan commented on MYFACES-3542: This problem may be solved now with the new visit algorithm. Leonardo responded before this change. I will check the problem is still there with current jsf 2.2. The render attribute of AjaxBehavior should support late value expression evaluation Key: MYFACES-3542 URL: https://issues.apache.org/jira/browse/MYFACES-3542 Project: MyFaces Core Issue Type: New Feature Reporter: Bernd Bohmann Attachments: late-render-expression-0.png, late-render-expression-1.png, late-render-expression-2.png, late-render-expression-3.png, late-render-expression-4.png, late-render-expression.tgz The render attribute of AjaxBehavior should evaluated during post-back after 'Invoke Application' and before 'Render Response'. It's easly to add this feature with a own PartialViewContext. But there is no call to processPartial with 'Invoke Application'. The Phase 'Render Response' is too late if you are using c:if to skip components from the component tree. See attached example app and pictures. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MYFACES-3542) The render attribute of AjaxBehavior should support late value expression evaluation
[ https://issues.apache.org/jira/browse/MYFACES-3542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13776393#comment-13776393 ] Leonardo Uribe commented on MYFACES-3542: - It is not solved in JSF 2.2 spec. The spec is silent in this regard. I still believe this should be discussed on the EG before do anything. Maybe this is something for 2.3. The render attribute of AjaxBehavior should support late value expression evaluation Key: MYFACES-3542 URL: https://issues.apache.org/jira/browse/MYFACES-3542 Project: MyFaces Core Issue Type: New Feature Reporter: Bernd Bohmann Attachments: late-render-expression-0.png, late-render-expression-1.png, late-render-expression-2.png, late-render-expression-3.png, late-render-expression-4.png, late-render-expression.tgz The render attribute of AjaxBehavior should evaluated during post-back after 'Invoke Application' and before 'Render Response'. It's easly to add this feature with a own PartialViewContext. But there is no call to processPartial with 'Invoke Application'. The Phase 'Render Response' is too late if you are using c:if to skip components from the component tree. See attached example app and pictures. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MYFACES-3542) The render attribute of AjaxBehavior should support late value expression evaluation
[ https://issues.apache.org/jira/browse/MYFACES-3542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13286644#comment-13286644 ] Leonardo Uribe commented on MYFACES-3542: - This is an interesting piece of code. I'll describe what I can see, I know you already know this but I'm just trying to follow the steps. In theory, org.apache.myfaces.renderkit.html.HtmlAjaxBehaviorRenderer look for the components, get its clientIds, and finally pass them as params when writing the js code related to the ajax operation. In this case, the values passed in javax.faces.partial.render request parameter, which are the same that were calculated before are just ignored, and the values used for identify the affected client behavior, which are used in the decode process (see org.apache.myfaces.shared.renderkit.html.HtmlRendererUtils.decodeClientBehaviors() ), are used to calculate the affected components, but the good part is if you use c:if to skip components from the component tree, they will not be used. There is not any reference in the spec about this. In theory, include it will not cause any side effects more than solve the problem described here. The only thing that suppose a problem is this propose a different behavior from the one found in the RI (Mojarra), maybe not thought by the EG when the spec was built. I don't know what to do in this case. A custom f:ajax component with this behavior in mind sounds better for me than change the default behavior. Any thoughts? The render attribute of AjaxBehavior should support late value expression evaluation Key: MYFACES-3542 URL: https://issues.apache.org/jira/browse/MYFACES-3542 Project: MyFaces Core Issue Type: New Feature Reporter: Bernd Bohmann Attachments: late-render-expression-0.png, late-render-expression-1.png, late-render-expression-2.png, late-render-expression-3.png, late-render-expression-4.png, late-render-expression.tgz The render attribute of AjaxBehavior should evaluated during post-back after 'Invoke Application' and before 'Render Response'. It's easly to add this feature with a own PartialViewContext. But there is no call to processPartial with 'Invoke Application'. The Phase 'Render Response' is too late if you are using c:if to skip components from the component tree. See attached example app and pictures. -- 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
