Author: SeanRogers Date: 2010-04-29 22:11:03 -0400 (Thu, 29 Apr 2010) New Revision: 16850 Modified: branches/enterprise/3.3.X/docs/userguide/en/src/main/docbook/modules/RFCarchitectover.xml branches/enterprise/3.3.X/docs/userguide/pom.xml Log: Updated circular reference information Modified: branches/enterprise/3.3.X/docs/userguide/en/src/main/docbook/modules/RFCarchitectover.xml =================================================================== --- branches/enterprise/3.3.X/docs/userguide/en/src/main/docbook/modules/RFCarchitectover.xml 2010-04-30 00:06:15 UTC (rev 16849) +++ branches/enterprise/3.3.X/docs/userguide/en/src/main/docbook/modules/RFCarchitectover.xml 2010-04-30 02:11:03 UTC (rev 16850) @@ -191,15 +191,11 @@ </listitem> <listitem> <para> - Certain components in the <property>RichFaces</property> framework allow data to be serialized and transferred from the server to the client. If the data model being used contains circular references, serialization of the data fails due to a stack overflow. + Certain components in the <property>RichFaces</property> framework allow data to be serialized and transferred from the server to the client. If the data model being used contains circular references, the references are partially serialized. Serialization of the data is done from the top-most object down, so all circular references back to parent objects are ignored when transferred to the client. </para> <para> - Circular references are unsupported and should be avoided; however, <xref linkend="Avoiding_Circular_References" /> shows how to prevent a stack overflow due to circular references. Serialization of the data is done from the top-most object down, and circular references back to parent objects are ignored. Access to non-serialized references to parent objects is not available using this method. + Only the data required by the client should be serialized. Serializing excess data can lead to performance and memory issues if too much data is processed, or security issues if private data is exposed to end-users. Large amounts of data can be handled creating Data Transfer Objects (<acronym>DTO</acronym>) from entities and passing them as suggestion values. Alternatively a mapping framework or assembler can manage the required data. </para> - <example id="Avoiding_Circular_References"> - <title>Avoiding Circular References</title> - <programlisting language="XML" role="XML">Code sample</programlisting> - </example> </listitem> </itemizedlist> </section> Modified: branches/enterprise/3.3.X/docs/userguide/pom.xml =================================================================== --- branches/enterprise/3.3.X/docs/userguide/pom.xml 2010-04-30 00:06:15 UTC (rev 16849) +++ branches/enterprise/3.3.X/docs/userguide/pom.xml 2010-04-30 02:11:03 UTC (rev 16850) @@ -620,7 +620,7 @@ org.richfaces.docs.common-resources </groupId> <artifactId> - ${project.translation} + ${translation} </artifactId> <version> ${project.version}