Author: SeanRogers Date: 2010-05-04 01:15:25 -0400 (Tue, 04 May 2010) New Revision: 16880 Added: branches/enterprise/3.3.X/docs/userguide/3.3.1.SP2.zip Modified: branches/enterprise/3.3.X/docs/userguide/en/src/main/docbook/included/calendar.xml branches/enterprise/3.3.X/docs/userguide/en/src/main/docbook/included/editor.xml branches/enterprise/3.3.X/docs/userguide/en/src/main/docbook/modules/RFCarchitectover.xml Log: docs bundle added temporarily Added: branches/enterprise/3.3.X/docs/userguide/3.3.1.SP2.zip =================================================================== (Binary files differ) Property changes on: branches/enterprise/3.3.X/docs/userguide/3.3.1.SP2.zip ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Modified: branches/enterprise/3.3.X/docs/userguide/en/src/main/docbook/included/calendar.xml =================================================================== --- branches/enterprise/3.3.X/docs/userguide/en/src/main/docbook/included/calendar.xml 2010-05-04 00:42:31 UTC (rev 16879) +++ branches/enterprise/3.3.X/docs/userguide/en/src/main/docbook/included/calendar.xml 2010-05-04 05:15:25 UTC (rev 16880) @@ -206,7 +206,10 @@ </emphasis> attributes were designed only for the &quot;<code>client</code>&quot; mode to load some data initially.</para> - </note> + </note> + <para> + Refer to <xref linkend="LimitationsAndRules" /> for limitations on serializing data. + </para> <para><emphasis> <property>&quot;ondateselect&quot;</property> </emphasis> attribute is used to define an event that is triggered Modified: branches/enterprise/3.3.X/docs/userguide/en/src/main/docbook/included/editor.xml =================================================================== --- branches/enterprise/3.3.X/docs/userguide/en/src/main/docbook/included/editor.xml 2010-05-04 00:42:31 UTC (rev 16879) +++ branches/enterprise/3.3.X/docs/userguide/en/src/main/docbook/included/editor.xml 2010-05-04 05:15:25 UTC (rev 16880) @@ -343,7 +343,14 @@ <programlisting role="XML"><![CDATA[... [Lorem ipsum=>http://mysite.com] *dolor sit* amet, ea _commodo_ consequat. ...]]></programlisting> - <para>Accordingly, if the Seam text is passed to the component it will be parsed to HTML code.</para> + <para>Accordingly, if the Seam text is passed to the component it will be parsed to HTML code.</para> + + <note> + <title><emphasis role="bold"> <property>&lt;rich:editor&gt;</property></emphasis> in <productname>Internet Explorer</productname></title> + <para> + When used in conjunction with a <emphasis role="bold"> <property>&lt;base&gt;</property></emphasis> HTML element containing an <varname>href</varname> attribute, the <emphasis role="bold"> <property>&lt;rich:editor&gt;</property></emphasis> will not be rendered correctly. Avoid using the <emphasis role="bold"> <property>&lt;base&gt;</property></emphasis> element and <varname>href</varname> attribute on pages containing a <emphasis role="bold"> <property>&lt;rich:editor&gt;</property></emphasis> component. + </para> + </note> </section> <section> 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-05-04 00:42:31 UTC (rev 16879) +++ branches/enterprise/3.3.X/docs/userguide/en/src/main/docbook/modules/RFCarchitectover.xml 2010-05-04 05:15:25 UTC (rev 16880) @@ -194,7 +194,7 @@ 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> - 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. + 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. Additionally, security issues may arise 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> </listitem> </itemizedlist> @@ -906,7 +906,7 @@ complex types including arrays and collections. The beans should be serializable to be refered with <emphasis> <property>&quot;data&quot;</property> - </emphasis> . </para> + </emphasis> . Refer to <xref linkend="LimitationsAndRules" /> for limitations on serializing data.</para> <para> There is a number of useful functions which can be used in JavaScript: </para> <itemizedlist> <listitem>