Author: SeanRogers Date: 2009-12-23 00:20:44 -0500 (Wed, 23 Dec 2009) New Revision: 16197 Added: root/docs/trunk/Component_Reference/en-US/images/figu-Component_Reference-richcolumn-Basic_column_example.png root/docs/trunk/Component_Reference/en-US/images/figu-Component_Reference-richcolumn-Column_spanning_example.png root/docs/trunk/Component_Reference/en-US/images/figu-Component_Reference-richcolumn-Row_spanning_example.png root/docs/trunk/Component_Reference/en-US/images/figu-Component_Reference-richcolumnGroup-Complex_headers_using_column_groups.png Modified: root/docs/trunk/Component_Reference/en-US/chap-Component_Reference-Actions.xml root/docs/trunk/Component_Reference/en-US/chap-Component_Reference-Common_Ajax_attributes.xml root/docs/trunk/Component_Reference/en-US/chap-Component_Reference-Containers.xml root/docs/trunk/Component_Reference/en-US/chap-Component_Reference-Introduction.xml root/docs/trunk/Component_Reference/en-US/chap-Component_Reference-Panels_and_containers.xml root/docs/trunk/Component_Reference/en-US/chap-Component_Reference-Processing_management.xml root/docs/trunk/Component_Reference/en-US/chap-Component_Reference-Validation.xml Log: Fixed rendering issues Modified: root/docs/trunk/Component_Reference/en-US/chap-Component_Reference-Actions.xml =================================================================== --- root/docs/trunk/Component_Reference/en-US/chap-Component_Reference-Actions.xml 2009-12-23 03:22:00 UTC (rev 16196) +++ root/docs/trunk/Component_Reference/en-US/chap-Component_Reference-Actions.xml 2009-12-23 05:20:44 UTC (rev 16197) @@ -64,9 +64,9 @@ The <varname>converter</varname> attribute can be used to specify how to convert the value before it is submitted to the data model. The property is assigned the new value during the <emphasis>Update Model</emphasis> phase. </para> <note> - <title>Note</title> + <title>Validation failure</title> <para> - If the validation of the form fails the <emphasis>Update Model</emphasis> phase will be skipped and the property will not be updated. + If the validation of the form fails, the <emphasis>Update Model</emphasis> phase will be skipped and the property will not be updated. </para> </note> <para> @@ -80,7 +80,7 @@ The <sgmltag>&lt;a4j:ajax&gt;</sgmltag> component allows Ajax capability to be added to any non-Ajax component. It is placed as a direct child to the component that requires Ajax support. The <sgmltag>&lt;a4j:ajax&gt;</sgmltag> component uses the common attributes listed in <xref linkend="chap-Component_Reference-Common_Ajax_attributes" />. </para> <note> - <title>Note</title> + <title>Attaching JavaScript functions</title> <para> When attaching the <sgmltag>&lt;a4j:ajax&gt;</sgmltag> component to non-Ajax JavaServer Faces command components, such as <sgmltag>&lt;h:commandButton&gt;</sgmltag> and <sgmltag>&lt;h:commandLink&gt;</sgmltag>, it is important to set <code>disabledDefault="true"</code>. If this attribute is not set, a non-Ajax request is sent after the Ajax request and the page is refreshed unexpectedly. </para> @@ -148,7 +148,7 @@ The <sgmltag>&lt;a4j:commandButton&gt;</sgmltag> requires only the <varname>value</varname> and <varname>render</varname> attributes to function. The <varname>value</varname> attribute specifies the text of the button and the <varname>render</varname> attribute specifies which areas are to be updated. The <sgmltag>&lt;a4j:commandButton&gt;</sgmltag> uses the <varname>onclick</varname> event instead of the <varname>onsubmit</varname> event, but otherwise uses all common Ajax attributes as listed in <xref linkend="chap-Component_Reference-Common_Ajax_attributes" />. </para> <note> - <title>Note</title> + <title>Set <code>disabledDefault="true"</code></title> <para> When attaching a JavaScript function to a <sgmltag>&lt;a4j:commandButton&gt;</sgmltag> with the help of a <sgmltag>&lt;rich:componentControl&gt;</sgmltag>, do not use the <varname>attachTo</varname> attribute of <sgmltag>&lt;rich:componentControl&gt;</sgmltag>. The attribute adds event handlers using <classname>Event.observe</classname> but <sgmltag>&lt;a4j:commandButton&gt;</sgmltag> does not include this event. </para> Modified: root/docs/trunk/Component_Reference/en-US/chap-Component_Reference-Common_Ajax_attributes.xml =================================================================== --- root/docs/trunk/Component_Reference/en-US/chap-Component_Reference-Common_Ajax_attributes.xml 2009-12-23 03:22:00 UTC (rev 16196) +++ root/docs/trunk/Component_Reference/en-US/chap-Component_Reference-Common_Ajax_attributes.xml 2009-12-23 05:20:44 UTC (rev 16197) @@ -40,7 +40,7 @@ The value of the <varname>render</varname> attribute can also be an expression written using JavaServer Faces' Expression Language (<acronym>EL</acronym>); this can either be a <type>Set</type>, <type>Collection</type>, <type>Array</type>, or <type>String</type>. </para> <important> - <title>Important</title> + <title><varname>rendered</varname> attributes</title> <para> A common problem with using <varname>render</varname> occurs when the referenced component has a <varname>rendered</varname> attribute. <acronym>JSF</acronym> does not mark the place in the browser's Document Object Model (<acronym>DOM</acronym>) where the rendered component would be placed in case the <varname>rendered</varname> attribute returns <literal>false</literal>. As such, when RichFaces sends the render code to the client, the page does not update as the place for the update is not known. </para> Modified: root/docs/trunk/Component_Reference/en-US/chap-Component_Reference-Containers.xml =================================================================== --- root/docs/trunk/Component_Reference/en-US/chap-Component_Reference-Containers.xml 2009-12-23 03:22:00 UTC (rev 16196) +++ root/docs/trunk/Component_Reference/en-US/chap-Component_Reference-Containers.xml 2009-12-23 05:20:44 UTC (rev 16197) @@ -34,7 +34,7 @@ The <sgmltag>&lt;a4j:form&gt;</sgmltag> builds on the functionality of the JavaServer Faces (<acronym>JSF</acronym>) component <sgmltag>&lt;h:form&gt;</sgmltag>, adding Ajax capabilities to the form. </para> <note> - <title>Note</title> + <title>Command link rendering fixed</title> <para> The <acronym>JSF</acronym> component <sgmltag>&lt;h:form&gt;</sgmltag>, on which the <sgmltag>&lt;a4j:form&gt;</sgmltag> component is based, had an issue whereby the <sgmltag>&lt;h:commandLink&gt;</sgmltag> component could not be re-rendered without re-rendering the entire form. <sgmltag>&lt;a4j:form&gt;</sgmltag> and <sgmltag>&lt;a4j:commandLink&gt;</sgmltag> fix this issue. </para> @@ -43,7 +43,7 @@ The <sgmltag>&lt;a4j:form&gt;</sgmltag> component can add indirect Ajax support to non-Ajax components on the form by setting <code>ajaxSubmit="true"</code>. It then uses the standard Ajax component attributes and updates components specified with the <varname>render</varname> attribute. </para> <important> - <title>Important</title> + <title><varname>ajaxSubmit</varname></title> <para> <sgmltag>&lt;a4j:form&gt;</sgmltag> should not use <code>ajaxSubmit="true"</code> if it contains other Ajax-capable components. </para> Modified: root/docs/trunk/Component_Reference/en-US/chap-Component_Reference-Introduction.xml =================================================================== --- root/docs/trunk/Component_Reference/en-US/chap-Component_Reference-Introduction.xml 2009-12-23 03:22:00 UTC (rev 16196) +++ root/docs/trunk/Component_Reference/en-US/chap-Component_Reference-Introduction.xml 2009-12-23 05:20:44 UTC (rev 16197) @@ -15,7 +15,7 @@ The RichFaces framework as it now stands is made up of two tag libraries: the <classname>a4j</classname> library and the <classname>rich</classname> library. The <classname>a4j</classname> tag library represents Ajax4jsf, which provides page-level Ajax support with core Ajax components. This allows developers to make use of custom Ajax behavior with existing components. The <classname>rich</classname> tag library provides Ajax support at the component level instead, and includes ready-made, self-contained components. These components don't require additional configuration in order to send requests or update. </para> <note> - <title>Note</title> + <title>Ajax support</title> <para> All components in the <classname>a4j</classname> library feature built-in Ajax support, so it is unnecessary to add the <sgmltag>&lt;a4j:ajax&gt;</sgmltag> behavior. </para> Modified: root/docs/trunk/Component_Reference/en-US/chap-Component_Reference-Panels_and_containers.xml =================================================================== --- root/docs/trunk/Component_Reference/en-US/chap-Component_Reference-Panels_and_containers.xml 2009-12-23 03:22:00 UTC (rev 16196) +++ root/docs/trunk/Component_Reference/en-US/chap-Component_Reference-Panels_and_containers.xml 2009-12-23 05:20:44 UTC (rev 16197) @@ -12,7 +12,7 @@ The <sgmltag>&lt;rich:modalPanel&gt;</sgmltag> component provides a modal panel or window that blocks interaction with the rest of the application while active. It can be easily positioned on the screen, dragged to a new position by the user, and re-sized. </para> <important> - <title>Important</title> + <title>Placement</title> <para> The <sgmltag>&lt;rich:modalPanel&gt;</sgmltag> component should always be placed outside the original <sgmltag>&lt;h:form&gt;</sgmltag>, and must include its own <sgmltag>&lt;h:form&gt;</sgmltag> if performing submissions. </para> @@ -103,7 +103,7 @@ The <sgmltag>&lt;rich:tabPanel&gt;</sgmltag> component provides a set of tabbed panels for displaying one panel of content at a time. The tabs can be highly customized and themed. </para> <note> - <title>Note</title> + <title>Form elements required</title> <para> All <sgmltag>&lt;rich:tabPanel&gt;</sgmltag> components should be wrapped in a form element so that content is correctly submitted. </para> Modified: root/docs/trunk/Component_Reference/en-US/chap-Component_Reference-Processing_management.xml =================================================================== --- root/docs/trunk/Component_Reference/en-US/chap-Component_Reference-Processing_management.xml 2009-12-23 03:22:00 UTC (rev 16196) +++ root/docs/trunk/Component_Reference/en-US/chap-Component_Reference-Processing_management.xml 2009-12-23 05:20:44 UTC (rev 16197) @@ -59,7 +59,7 @@ </listitem> </itemizedlist> <para> - The <sgmltag>&lt;a4j:queue&gt;</sgmltag> features several events relating to queuing actions: + The <sgmltag>&lt;a4j:queue&gt;</sgmltag> component features several events relating to queuing actions: </para> <itemizedlist> <listitem> Modified: root/docs/trunk/Component_Reference/en-US/chap-Component_Reference-Validation.xml =================================================================== --- root/docs/trunk/Component_Reference/en-US/chap-Component_Reference-Validation.xml 2009-12-23 03:22:00 UTC (rev 16196) +++ root/docs/trunk/Component_Reference/en-US/chap-Component_Reference-Validation.xml 2009-12-23 05:20:44 UTC (rev 16197) @@ -60,14 +60,14 @@ <programlisting language="XML" role="XML"> <xi:include href="extras/exam-Component_Reference-richajaxValidator-Using_richajaxValidator_with_Hibernate_Validator-0.xml_sample" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /> </programlisting> - </example> - <para> - The validation is performed using the <classname>ValidationBean</classname> class: - </para> + <para> + The validation is performed using the <classname>ValidationBean</classname> class: + </para> <programlisting language="Java" role="JAVA"> -<xi:include href="extras/exam-Component_Reference-exam-Component_Reference-ValidationBean.js" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /> +<xi:include href="extras/exam-Component_Reference-ValidationBean.js" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /> </programlisting> + </example> </section> <section id="sect-Component_Reference-Validation-richbeanValidator"> @@ -119,7 +119,7 @@ </para> <programlisting language="Java" role="JAVA"> -<xi:include href="extras/exam-Component_Reference-exam-Component_Reference-ValidationBean.js" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /> +<xi:include href="extras/exam-Component_Reference-ValidationBean.js" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /> </programlisting> </example> </section> Added: root/docs/trunk/Component_Reference/en-US/images/figu-Component_Reference-richcolumn-Basic_column_example.png =================================================================== (Binary files differ) Property changes on: root/docs/trunk/Component_Reference/en-US/images/figu-Component_Reference-richcolumn-Basic_column_example.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: root/docs/trunk/Component_Reference/en-US/images/figu-Component_Reference-richcolumn-Column_spanning_example.png =================================================================== (Binary files differ) Property changes on: root/docs/trunk/Component_Reference/en-US/images/figu-Component_Reference-richcolumn-Column_spanning_example.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: root/docs/trunk/Component_Reference/en-US/images/figu-Component_Reference-richcolumn-Row_spanning_example.png =================================================================== (Binary files differ) Property changes on: root/docs/trunk/Component_Reference/en-US/images/figu-Component_Reference-richcolumn-Row_spanning_example.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: root/docs/trunk/Component_Reference/en-US/images/figu-Component_Reference-richcolumnGroup-Complex_headers_using_column_groups.png =================================================================== (Binary files differ) Property changes on: root/docs/trunk/Component_Reference/en-US/images/figu-Component_Reference-richcolumnGroup-Complex_headers_using_column_groups.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream