Author: artdaw Date: 2008-08-04 04:54:49 -0400 (Mon, 04 Aug 2008) New Revision: 9878 Modified: trunk/docs/userguide/en/src/main/docbook/modules/RFCarchitectover.xml Log: https://jira.jboss.org/jira/browse/RF-3892 - State Manager API section done Modified: trunk/docs/userguide/en/src/main/docbook/modules/RFCarchitectover.xml =================================================================== --- trunk/docs/userguide/en/src/main/docbook/modules/RFCarchitectover.xml 2008-08-04 08:54:25 UTC (rev 9877) +++ trunk/docs/userguide/en/src/main/docbook/modules/RFCarchitectover.xml 2008-08-04 08:54:49 UTC (rev 9878) @@ -4419,6 +4419,16 @@ So you could define input fields values, controls labels, actions, rendering conditions, etc. using the same state variables which have different values for every State. </para> + <figure> + <title> + RichFaces State API + </title> + <mediaobject> + <imageobject> + <imagedata fileref="images/stateapi3.png"/> + </imageobject> + </mediaobject> + </figure> <para> Actually States is a <property>map</property> where the entry key is name of the State and the value is a State map. Concrete State map has entries with some names as keys and any objects as values. @@ -4479,10 +4489,10 @@ </managed-bean> ...]]></programlisting> <para> - One bean (<code>org.richfaces.demo.stateApi.Config</code>) defines and stores states. + One bean (&quot;config&quot;) defines and stores states. </para> <para> - The other bean (<code>org.richfaces.ui.model.States</code>) with the type <code>org.richfaces.ui.model.States</code> has + The other bean (&quot;state&quot;) with the type <code>org.richfaces.ui.model.States</code> has the &quot;states&quot; managed property that is bound to the &quot;config&quot; bean which defines states. </para> </listitem>