Author: ilya_shaikovsky Date: 2008-04-25 08:28:26 -0400 (Fri, 25 Apr 2008) New Revision: 8172 Modified: trunk/samples/richfaces-demo/src/main/webapp/richfaces/keepAlive/examples/enabledIssue.xhtml Log: http://jira.jboss.com/jira/browse/RF-3203 Modified: trunk/samples/richfaces-demo/src/main/webapp/richfaces/keepAlive/examples/enabledIssue.xhtml =================================================================== --- trunk/samples/richfaces-demo/src/main/webapp/richfaces/keepAlive/examples/enabledIssue.xhtml 2008-04-25 12:24:51 UTC (rev 8171) +++ trunk/samples/richfaces-demo/src/main/webapp/richfaces/keepAlive/examples/enabledIssue.xhtml 2008-04-25 12:28:26 UTC (rev 8172) @@ -18,13 +18,13 @@ <f:verbatim> This example <b>will not work</b> as expected. The expression for 'disabled' attribute - equals true only after UPDATE model phase when the rsBean properties are + equals <i>false</i> only after UPDATE model phase when the rsBean properties are updated with submitted values. So, the component is rendered as enabled on the RENDER RESPONSE phase.<br /> However, those values do not make sence during the next Ajax request. The rsBean is created from scratch as soon as it is a new request. JSF makes a decision what is process on the second (APPLY VALUES) phase. At this moment, - the expression for 'disabled' still equals false. Therefore, the processing + the expression for 'disabled' still equals true. Therefore, the processing for button is bypassed. The action does not invoked as a result. phase<br/><br/> </f:verbatim>