Author: euhvasko
Date: 2007-09-25 09:27:21 -0400 (Tue, 25 Sep 2007)
New Revision: 3095
Modified:
trunk/docs/userguide/en/src/main/docbook/included/outputPanel.xml
trunk/docs/userguide/en/src/main/docbook/included/region.xml
Log:
http://jira.jboss.com/jira/browse/RF-622 changed Ajax4jsf to RichFaces
Modified: trunk/docs/userguide/en/src/main/docbook/included/outputPanel.xml
===================================================================
--- trunk/docs/userguide/en/src/main/docbook/included/outputPanel.xml 2007-09-25 13:11:58
UTC (rev 3094)
+++ trunk/docs/userguide/en/src/main/docbook/included/outputPanel.xml 2007-09-25 13:27:21
UTC (rev 3095)
@@ -62,9 +62,9 @@
<title>Key attributes and ways of usage</title>
<para><emphasis
role="bold"><property><a4j:outPanel></property></emphasis>
allows marking of a page area, which is updated on Ajax response. Anyway, <emphasis
role="bold">
<property><a4j:outputPanel></property>
- </emphasis> usage is optional, as in Ajax4jsf it's possible to
indicate any existing component id on a component view in order to define updating areas.
+ </emphasis> usage is optional, as in RichFaces it's possible to
indicate any existing component id on a component view in order to define updating areas.
-To speed up the performance, Ajax4jsf updates only a component tree. <emphasis
role="bold">
+To speed up the performance, RichFaces updates only a component tree. <emphasis
role="bold">
<property><a4j:outputPanel></property>
</emphasis> usage is recommended for wrapping components that aren't
rendered during the primary non-ajax response, as the components don't present in
a component tree.
</para>
@@ -115,12 +115,12 @@
</a4j:outputPanel>
]]></programlisting>
<para>As you see, the code is very similar to the one shown above, but
<emphasis ><property>"reRender
"</property></emphasis> attribute refers directly to the updating
panelGrid and not to the framing outputPanel, and it's more semantically
correct.</para>
- <para><emphasis
role="bold"><property><a4j:outPanel></property></emphasis>
should be used for non-JSF component part framing, which is to be updated on Ajax
response, as Ajax4jsf specifies the list of updating areas as a list of an existing JSF
component. </para>
- <para>On default non-JSF context isn't saved in a component tree, but
is rendered anew every time. To accelerate the processing speed and Ajax response input
speed, Ajax4jsf saves non-JSF context in a component tree on default. This option could be
canceled by<emphasis><property> "keepTransient"
</property></emphasis>attribute that cancels transient flag forced setting for
child components. This flag setting keeps the current value set by child
components.</para>
+ <para><emphasis
role="bold"><property><a4j:outPanel></property></emphasis>
should be used for non-JSF component part framing, which is to be updated on Ajax
response, as RichFaces specifies the list of updating areas as a list of an existing JSF
component. </para>
+ <para>On default non-JSF context isn't saved in a component tree, but
is rendered anew every time. To accelerate the processing speed and Ajax response input
speed, RichFaces saves non-JSF context in a component tree on default. This option could
be canceled by<emphasis><property> "keepTransient"
</property></emphasis>attribute that cancels transient flag forced setting for
child components. This flag setting keeps the current value set by child
components.</para>
<para>Note: In JSF 1.1 implementation and lower, where non-JSF context should
be framed with the "f:verbatim" attribute, <emphasis
role="bold">
<property><a4j:outputPanel></property>
- </emphasis> doesn't improve this JSF implementation option in any
way, so you still have to use this tag where it's necessary without Ajax4jsf
usage. </para>
- <para>Ajax4jsf allows setting Ajax responses rendering directly basing on
component tree nodes without referring to the JSP (XHTML) page code. It could be defined
by selfRendered attribute setting to <emphasis >
+ </emphasis> doesn't improve this JSF implementation option in any
way, so you still have to use this tag where it's necessary without RichFaces
usage. </para>
+ <para>RichFaces allows setting Ajax responses rendering directly basing on
component tree nodes without referring to the JSP (XHTML) page code. It could be defined
by selfRendered attribute setting to <emphasis >
<property>"true"</property>
</emphasis>
on <emphasis role="bold">
Modified: trunk/docs/userguide/en/src/main/docbook/included/region.xml
===================================================================
--- trunk/docs/userguide/en/src/main/docbook/included/region.xml 2007-09-25 13:11:58 UTC
(rev 3094)
+++ trunk/docs/userguide/en/src/main/docbook/included/region.xml 2007-09-25 13:27:21 UTC
(rev 3095)
@@ -85,7 +85,7 @@
<!--..Some content that will be decoded on server after Ajax request.-->
</a4j:region >]]></programlisting>
<para>Therefore, the external region is decoded for the
"link1" and the internal one is decoded for the
"link2".</para>
- <para>Ajax4jsf allows setting Ajax responses rendering directly basing on
component tree nodes without referring to the JSP (XHTML) page code. It could be defined
by<emphasis><property> "selfRendered"
</property></emphasis>attribute setting to
<emphasis><property>"true"</property></emphasis>
on <emphasis role="bold">
+ <para>RichFaces allows setting Ajax responses rendering directly basing on
component tree nodes without referring to the JSP (XHTML) page code. It could be defined
by<emphasis><property> "selfRendered"
</property></emphasis>attribute setting to
<emphasis><property>"true"</property></emphasis>
on <emphasis role="bold">
<property><a4j:region></property>
</emphasis> and could help considerably speed up a response output. However,
this rapid processing could cause missing of transient components that present on view and
don't come into a component tree as well as omitting of <emphasis
role="bold">
<property><a4j:outputPanel></property>
@@ -96,7 +96,7 @@
<a4j:commandLink reRender="someID" value="Link"
id="link1"/>
<!--..Some content with HTML used ("br" ,"h1" and other tags
used)-->
</a4j:region >]]></programlisting>
- <para>In this case, the processing is quicker and going on without referring to
a page code, but the HTML code that isn't saved in a component tree could be
lost. Thus, this optimization should be very carefully performed and a usage of the
additional components ajax4jsf (<emphasis
role="bold"><property><a4j:outputPanel></property></emphasis>)
is required. </para>
+ <para>In this case, the processing is quicker and going on without referring to
a page code, but the HTML code that isn't saved in a component tree could be
lost. Thus, this optimization should be very carefully performed and a usage of the
additional components RichFaces (<emphasis
role="bold"><property><a4j:outputPanel></property></emphasis>)
is required. </para>
<para>The processing could be also accelerated if a region decoded for the
processing passes straight away into Encode. But to update some data out of the region or
on another region, use the <emphasis >
<property>"renderRegionOnly"</property>
</emphasis>