Author: mmcallis Date: 2008-07-12 03:47:54 -0400 (Sat, 12 Jul 2008) New Revision: 11421 Modified: docs/branches/JBoss_Portal_Branch_2_7/referenceGuide/en/modules/clustering.xml docs/branches/JBoss_Portal_Branch_2_7/referenceGuide/en/modules/contentintegration.xml docs/branches/JBoss_Portal_Branch_2_7/referenceGuide/en/modules/portalapi.xml Log: - code highlighting - scalefit - 13.4. Setup: removed <note> (they should not span multiple pages) Modified: docs/branches/JBoss_Portal_Branch_2_7/referenceGuide/en/modules/clustering.xml =================================================================== --- docs/branches/JBoss_Portal_Branch_2_7/referenceGuide/en/modules/clustering.xml 2008-07-12 07:30:35 UTC (rev 11420) +++ docs/branches/JBoss_Portal_Branch_2_7/referenceGuide/en/modules/clustering.xml 2008-07-12 07:47:54 UTC (rev 11421) @@ -64,7 +64,7 @@ <ulink url="http://labs.jboss.com/jbossas/docs/">clustering documentation</ulink>. </note> <imageobject> - <imagedata fileref="images/clustering/overview.png" format="png"/> + <imagedata fileref="images/clustering/overview.png" format="png" scalefit="1"/> </imageobject> </para> </sect1> @@ -245,10 +245,13 @@ <para>Copy JBoss Portal HA to the deploy directory of the two configurations.</para> <!-- adding instruction about jboss cache versioning --> - <note> + <formalpara> + <title>JBoss Cache</title> <para> To improve CMS performance JBoss Cache is leveraged to cache the content cluster wide. We recommend that you use the following version of JBoss Cache for best performance: + </para> +</formalpara> <itemizedlist> <listitem> <emphasis>JBoss Cache 1.4.0.SP1 and above</emphasis> @@ -257,6 +260,7 @@ <emphasis>JGroups 2.2.7 or 2.2.8</emphasis> </listitem> </itemizedlist> + <para> When building from source the following command: <literal>{core}/build.xml deploy-ha</literal> automatically upgrades your JBoss Cache version. </para> @@ -268,7 +272,8 @@ Replace the following configuration in the <emphasis>cms.pm.cache:service=TreeCache</emphasis> Mbean: - <programlisting><![CDATA[ + </para> + <programlisting role="XML"><![CDATA[ <!-- Configuring the PortalCMSCacheLoader CacheLoader configuration for 1.4.0 @@ -288,8 +293,10 @@ </config> </attribute>]]> </programlisting> + <para> with the following configuration: - <programlisting><![CDATA[ + </para> + <programlisting role="XML"><![CDATA[ <!-- Configuring the PortalCMSCacheLoader CacheLoader configuratoon for 1.2.4SP2 @@ -302,13 +309,9 @@ <attribute name="CacheLoaderShared">false</attribute> <attribute name="CacheLoaderFetchTransientState">false</attribute> <attribute name="CacheLoaderFetchPersistentState">false</attribute> -<attribute name="CacheLoaderAsynchronous">false</attribute> ]]></programlisting> +<attribute name="CacheLoaderAsynchronous">false</attribute>]]></programlisting> - </para> - </note> - - - <para>Finally we can start both servers, open two shells and execute : +<para>Finally we can start both servers, open two shells and execute : <programlisting><![CDATA[ Modified: docs/branches/JBoss_Portal_Branch_2_7/referenceGuide/en/modules/contentintegration.xml =================================================================== --- docs/branches/JBoss_Portal_Branch_2_7/referenceGuide/en/modules/contentintegration.xml 2008-07-12 07:30:35 UTC (rev 11420) +++ docs/branches/JBoss_Portal_Branch_2_7/referenceGuide/en/modules/contentintegration.xml 2008-07-12 07:47:54 UTC (rev 11421) @@ -21,7 +21,7 @@ to the user.</note> <mediaobject> <imageobject> - <imagedata align="center" fileref="images/content/before.png" format="png"/> + <imagedata align="center" fileref="images/content/before.png" format="png" scalefit="1"/> </imageobject> <caption> <para>The portal uses portlets to configure content</para> @@ -29,7 +29,7 @@ </mediaobject> <mediaobject> <imageobject> - <imagedata align="center" fileref="images/content/after.png" format="png"/> + <imagedata align="center" fileref="images/content/after.png" format="png" scalefit="1"/> </imageobject> <caption> <para>The portal references directly the content and use portlet to interact with content</para> @@ -71,7 +71,7 @@ defined content, often the two modes will display the same thing. The traditional edit mode is not used because the edit mode is more targeted to configure how the portlet shows content to the end user rather than what content it shows.</para> <imageobject> - <imagedata align="center" fileref="images/content/cms.png" format="png"/> + <imagedata align="center" fileref="images/content/cms.png" format="png" scalefit="1"/> </imageobject> <caption>Example of content customization - CMS Portlet</caption> </sect1> @@ -211,7 +211,7 @@ <para>The editor is probably the longest part of the portlet. It tries to stay simple though and goes directly to the point.</para> <imageobject> - <imagedata align="center" fileref="images/content/fs1.png" format="png"/> + <imagedata align="center" fileref="images/content/fs1.png" format="png" scalefit="1"/> </imageobject> <caption>Content editor of FSContentDrivenPortlet in action</caption> <programlisting><![CDATA[ @@ -360,7 +360,7 @@ <sect3> <title>Hooking the portlet into the portal</title> <imageobject> - <imagedata align="center" fileref="images/content/fs2.png" format="png"/> + <imagedata align="center" fileref="images/content/fs2.png" format="png" scalefit="1"/> </imageobject> <caption>Management portlet with <emphasis>filesystem</emphasis> content type enabled</caption> <para>Finally we need to make the portal aware of the fact that the portlet can edit and interpret content. For that Modified: docs/branches/JBoss_Portal_Branch_2_7/referenceGuide/en/modules/portalapi.xml =================================================================== --- docs/branches/JBoss_Portal_Branch_2_7/referenceGuide/en/modules/portalapi.xml 2008-07-12 07:30:35 UTC (rev 11420) +++ docs/branches/JBoss_Portal_Branch_2_7/referenceGuide/en/modules/portalapi.xml 2008-07-12 07:47:54 UTC (rev 11421) @@ -240,7 +240,7 @@ a corresponding event will be fired.</para> <mediaobject> <imageobject> - <imagedata align="center" fileref="images/portalapi/PortalNodeEvent.png" format="png"/> + <imagedata align="center" fileref="images/portalapi/PortalNodeEvent.png" format="png" scalefit="1"/> </imageobject> <caption> <para>The portal node event class hierarchy</para>