Author: smukhina Date: 2007-08-31 06:52:14 -0400 (Fri, 31 Aug 2007) New Revision: 2640 Modified: trunk/docs/userguide/en/src/main/docbook/included/ajaxListener.xml trunk/docs/userguide/en/src/main/docbook/included/jsFunction.xml trunk/docs/userguide/en/src/main/docbook/included/tooltip.xml trunk/docs/userguide/en/src/main/docbook/modules/RFCarchitectover.xml trunk/docs/userguide/en/src/main/docbook/modules/RFCfaq.xml Log: http://jira.jboss.com/jira/browse/RF-398 So -> Thus, Hence Modified: trunk/docs/userguide/en/src/main/docbook/included/ajaxListener.xml =================================================================== --- trunk/docs/userguide/en/src/main/docbook/included/ajaxListener.xml 2007-08-31 10:20:19 UTC (rev 2639) +++ trunk/docs/userguide/en/src/main/docbook/included/ajaxListener.xml 2007-08-31 10:52:14 UTC (rev 2640) @@ -62,7 +62,7 @@ <emphasis role="bold"><property>&lt;a4j:ajaxListener&gt;</property> </emphasis>). Ajax Listener is invoked before the Render Response phase. Instead of Action Listener of Value Change Listener which are not -invoked when Validation of Update Model phases failed, Ajax Listener is guarantied to be invoked for each Ajax response. So, it is +invoked when Validation of Update Model phases failed, Ajax Listener is guarantied to be invoked for each Ajax response. Thus, it is a good place for update the list of re-rendered components, for example. Ajax Listener is not invoked for non-Ajax request and when RichFaces works in "Ajax Request generates Non-Ajax Response" mode. Therefore, Ajax Listener invocation is a good indicator that Ajax response is going to be processed. Modified: trunk/docs/userguide/en/src/main/docbook/included/jsFunction.xml =================================================================== --- trunk/docs/userguide/en/src/main/docbook/included/jsFunction.xml 2007-08-31 10:20:19 UTC (rev 2639) +++ trunk/docs/userguide/en/src/main/docbook/included/jsFunction.xml 2007-08-31 10:52:14 UTC (rev 2640) @@ -68,7 +68,7 @@ <section> <title>Key attributes and ways of usage</title> <para> As the component uses Ajax request to get data from server - it has all common Ajax - Action attributes. So, action and actionListener can be invoked, and reRendering some parts of + Action attributes. Hence, action and actionListener can be invoked, and reRendering some parts of the page fired after calling function. </para> <para> When using the <emphasis role="bold"> <property>&lt;a4j:jsFunction&gt;</property> @@ -103,7 +103,7 @@ <property>&lt;a4j:commandButton&gt;</property> </emphasis>, but it could be activated from the JavaScript code. It allows to invoke some server side functionality and use the returned data in the JavaScript function invoked from - <emphasis><property>&quot;oncomplete&quot;</property></emphasis> attribute. So it&apos;s possible to use <emphasis + <emphasis><property>&quot;oncomplete&quot;</property></emphasis> attribute. Hence it&apos;s possible to use <emphasis role="bold"> <property>&lt;a4j:jsFunction&gt;</property> </emphasis> instead of <emphasis role="bold"> Modified: trunk/docs/userguide/en/src/main/docbook/included/tooltip.xml =================================================================== --- trunk/docs/userguide/en/src/main/docbook/included/tooltip.xml 2007-08-31 10:20:19 UTC (rev 2639) +++ trunk/docs/userguide/en/src/main/docbook/included/tooltip.xml 2007-08-31 10:52:14 UTC (rev 2640) @@ -77,7 +77,7 @@ </para> <para> There is possibility to define a facet with name &quot;defaultContent&quot;. This facet provides default content to be -displayed while main content loaded to the page in Ajax mode. So after <property>tooltip</property> called in Ajax mode - it +displayed while main content loaded to the page in Ajax mode. Thus after <property>tooltip</property> called in Ajax mode - it appeared with the content defined in the facet and after loading complete content changes to loaded one. </para> <para> Modified: trunk/docs/userguide/en/src/main/docbook/modules/RFCarchitectover.xml =================================================================== --- trunk/docs/userguide/en/src/main/docbook/modules/RFCarchitectover.xml 2007-08-31 10:20:19 UTC (rev 2639) +++ trunk/docs/userguide/en/src/main/docbook/modules/RFCarchitectover.xml 2007-08-31 10:52:14 UTC (rev 2640) @@ -18,7 +18,7 @@ <para>The framework is implemented as a component library which adds Ajax capability into existing pages, so you don&apos;t need to write any JavaScript code or to replace existing components with new Ajax widgets. <property>RichFaces</property> enables page-wide Ajax support instead of the - traditional component-wide support. So, you can define the event on the page that + traditional component-wide support. Hence, you can define the event on the page that invokes an Ajax request and the areas of the page that should be synchronized with the JSF Component Tree after the Ajax request changes the data on the server according to the events fired on the client.</para> @@ -120,7 +120,7 @@ </emphasis> for self-rendered containers, since this component is transient and not saved in the tree. </listitem> <listitem> - Ajax requests are made by XMLHttpRequest functions in XML format, but this XML bypasses most validations and the corrections that might be made in a browser. So, create only a strict standards-compliant code for HTML and XHTML, without skipping any required elements or attributes. Any necessary XML corrections are automatically made by the XML filter on the server, but lot&apos;s of unexpected effects can be produced by an incorrect HTML code. + Ajax requests are made by XMLHttpRequest functions in XML format, but this XML bypasses most validations and the corrections that might be made in a browser. Thus, create only a strict standards-compliant code for HTML and XHTML, without skipping any required elements or attributes. Any necessary XML corrections are automatically made by the XML filter on the server, but lot&apos;s of unexpected effects can be produced by an incorrect HTML code. </listitem> </itemizedlist> </section> Modified: trunk/docs/userguide/en/src/main/docbook/modules/RFCfaq.xml =================================================================== --- trunk/docs/userguide/en/src/main/docbook/modules/RFCfaq.xml 2007-08-31 10:20:19 UTC (rev 2639) +++ trunk/docs/userguide/en/src/main/docbook/modules/RFCfaq.xml 2007-08-31 10:52:14 UTC (rev 2640) @@ -178,7 +178,7 @@ <title>Does RichFaces work with facelets?</title> <para>Main <ulink url="http://livedemo.exadel.com/richfaces-demo/"> demo</ulink> of RichFaces is a facelets based application. Full Facelets support is one of - the main features. So, the answer is yes.</para> + the main features. Hence, the answer is yes.</para> </section> <section> @@ -186,7 +186,7 @@ <title>Is it possible to create dynamic menu using &lt;rich:dropDownMenu&gt; component?</title> <para><emphasis role="bold">&lt;rich:dropDownMenu&gt;</emphasis> is a - standard JSF component. So, creation of the menu dynamically from the Java + standard JSF component. Thus, creation of the menu dynamically from the Java Script code is the same as for any other jsf component.</para> <para>For more information follow the <ulink url="http://www.jboss.com/index.html?module=bb&amp;op=viewtopic&...