Author: ilya_shaikovsky
Date: 2008-08-06 07:20:30 -0400 (Wed, 06 Aug 2008)
New Revision: 9938
Modified:
trunk/samples/richfaces-demo/src/main/webapp/richfaces/ajaxAttributes/usage.xhtml
Log:
Modified:
trunk/samples/richfaces-demo/src/main/webapp/richfaces/ajaxAttributes/usage.xhtml
===================================================================
---
trunk/samples/richfaces-demo/src/main/webapp/richfaces/ajaxAttributes/usage.xhtml 2008-08-06
11:11:24 UTC (rev 9937)
+++
trunk/samples/richfaces-demo/src/main/webapp/richfaces/ajaxAttributes/usage.xhtml 2008-08-06
11:20:30 UTC (rev 9938)
@@ -150,6 +150,27 @@
current component (along with <i>f:param</i> or
<i>a4j:actionparam</i> values if any).
In case of a4j:support, it will be a value of the parent component.
</p>
+ <p>
+ <b>process</b> attribute allows you to define the components to be
processed
+ additionally with the component which marked as ajaxSingle or wrapped to region.
+ Imagine you need to process only two field in the different parts of view.
+ If you wrap the first to region or make nested support component ajaxSingle -
+ second component will not be processed. And if you do not define first component
+ in this way - all the view will be processed. In this case next simple constructions
+ should be used:
+ </p>
+ <fieldset class="demo_fieldset">
+ <legend class="demo_legend">Code Example</legend>
+ <rich:panel styleClass="viewsourcepanel" bodyClass="viewsourcebody
rich-laguna-panel-no-header">
+ <rich:insert src="/richfaces/ajaxAttributes/snippets/process.xhtml"
highlight="xhtml"></rich:insert>
+ </rich:panel>
+ </fieldset>
+ <p>
+ In this case when the name field will loose focus - Ajax request will be sent.
+ And only two fields (<i>name</i> and additionally
<i>email</i>) will be processed
+ (decoding, conversion/validation, value applying will be executed). The same
+ for the <i>email</i> field blur event.
+ </p>
<p><b>immediate</b> attribute has the same purpose as any other
non-Ajax-JSF component.
The default ActionListener should be executed immediately (i.e. during the Apply
Request
Values phase of a request processing lifecycle), rather than waiting until the