From portal-commits at lists.jboss.org Sat Jul 12 03:47:55 2008
Content-Type: multipart/mixed; boundary="===============1109069396435649634=="
MIME-Version: 1.0
From: portal-commits at lists.jboss.org
To: portal-commits at lists.jboss.org
Subject: [portal-commits] JBoss Portal SVN: r11421 -
 docs/branches/JBoss_Portal_Branch_2_7/referenceGuide/en/modules.
Date: Sat, 12 Jul 2008 03:47:54 -0400
Message-ID: <E1KHZpi-0002IZ-TS@committer01.frg.pub.inap.atl.jboss.com>

--===============1109069396435649634==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

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/clusteri=
ng.xml
   docs/branches/JBoss_Portal_Branch_2_7/referenceGuide/en/modules/contenti=
ntegration.xml
   docs/branches/JBoss_Portal_Branch_2_7/referenceGuide/en/modules/portalap=
i.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/c=
lustering.xml
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- docs/branches/JBoss_Portal_Branch_2_7/referenceGuide/en/modules/cluster=
ing.xml	2008-07-12 07:30:35 UTC (rev 11420)
+++ docs/branches/JBoss_Portal_Branch_2_7/referenceGuide/en/modules/cluster=
ing.xml	2008-07-12 07:47:54 UTC (rev 11421)
@@ -64,7 +64,7 @@
             <ulink url=3D"http://labs.jboss.com/jbossas/docs/">clustering =
documentation</ulink>.
          </note>
          <imageobject>
-            <imagedata fileref=3D"images/clustering/overview.png" format=
=3D"png"/>
+            <imagedata fileref=3D"images/clustering/overview.png" format=
=3D"png" scalefit=3D"1"/>
          </imageobject>
       </para>
    </sect1>
@@ -245,10 +245,13 @@
       <para>Copy JBoss Portal HA to the deploy directory of the two config=
urations.</para>
 =

       <!--  adding instruction about jboss cache versioning -->
-       <note>
+      <formalpara>
+	      <title>JBoss Cache</title>
            <para>
                To improve CMS performance JBoss Cache is leveraged to cach=
e the content cluster wide.
                We recommend that you use the following version of JBoss Ca=
che 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=3DTreeCache</emphasis>
                Mbean:
-               <programlisting><![CDATA[
+       </para>
+               <programlisting role=3D"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=3D"XML"><![CDATA[
 <!--
    Configuring the PortalCMSCacheLoader
    CacheLoader configuratoon for 1.2.4SP2
@@ -302,13 +309,9 @@
 <attribute name=3D"CacheLoaderShared">false</attribute>
 <attribute name=3D"CacheLoaderFetchTransientState">false</attribute>
 <attribute name=3D"CacheLoaderFetchPersistentState">false</attribute>
-<attribute name=3D"CacheLoaderAsynchronous">false</attribute>        ]]></=
programlisting>
+<attribute name=3D"CacheLoaderAsynchronous">false</attribute>]]></programl=
isting>
 =

-           </para>
-       </note>
-
-
-       <para>Finally we can start both servers, open two shells and execut=
e :
+<para>Finally we can start both servers, open two shells and execute :
          <programlisting><![CDATA[
 >cd $JBOSS_HOME/bin
 >sh run.sh -c ports-01

Modified: docs/branches/JBoss_Portal_Branch_2_7/referenceGuide/en/modules/c=
ontentintegration.xml
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- docs/branches/JBoss_Portal_Branch_2_7/referenceGuide/en/modules/content=
integration.xml	2008-07-12 07:30:35 UTC (rev 11420)
+++ docs/branches/JBoss_Portal_Branch_2_7/referenceGuide/en/modules/content=
integration.xml	2008-07-12 07:47:54 UTC (rev 11421)
@@ -21,7 +21,7 @@
    to the user.</note>
    <mediaobject>
       <imageobject>
-         <imagedata align=3D"center" fileref=3D"images/content/before.png"=
 format=3D"png"/>
+         <imagedata align=3D"center" fileref=3D"images/content/before.png"=
 format=3D"png" scalefit=3D"1"/>
       </imageobject>
       <caption>
          <para>The portal uses portlets to configure content</para>
@@ -29,7 +29,7 @@
    </mediaobject>
    <mediaobject>
       <imageobject>
-         <imagedata align=3D"center" fileref=3D"images/content/after.png" =
format=3D"png"/>
+         <imagedata align=3D"center" fileref=3D"images/content/after.png" =
format=3D"png" scalefit=3D"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. Th=
e traditional edit mode is not used because the edit mode
       is more targeted to configure how the portlet shows content to the e=
nd user rather than what content it shows.</para>
       <imageobject>
-         <imagedata align=3D"center" fileref=3D"images/content/cms.png" fo=
rmat=3D"png"/>
+         <imagedata align=3D"center" fileref=3D"images/content/cms.png" fo=
rmat=3D"png" scalefit=3D"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=3D"center" fileref=3D"images/content/fs1.p=
ng" format=3D"png"/>
+               <imagedata align=3D"center" fileref=3D"images/content/fs1.p=
ng" format=3D"png" scalefit=3D"1"/>
             </imageobject>
             <caption>Content editor of FSContentDrivenPortlet in action</c=
aption>
             <programlisting><![CDATA[
@@ -360,7 +360,7 @@
          <sect3>
             <title>Hooking the portlet into the portal</title>
             <imageobject>
-               <imagedata align=3D"center" fileref=3D"images/content/fs2.p=
ng" format=3D"png"/>
+               <imagedata align=3D"center" fileref=3D"images/content/fs2.p=
ng" format=3D"png" scalefit=3D"1"/>
             </imageobject>
             <caption>Management portlet with <emphasis>filesystem</emphasi=
s> content type enabled</caption>
             <para>Finally we need to make the portal aware of the fact tha=
t the portlet can edit and interpret content. For that

Modified: docs/branches/JBoss_Portal_Branch_2_7/referenceGuide/en/modules/p=
ortalapi.xml
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- docs/branches/JBoss_Portal_Branch_2_7/referenceGuide/en/modules/portala=
pi.xml	2008-07-12 07:30:35 UTC (rev 11420)
+++ docs/branches/JBoss_Portal_Branch_2_7/referenceGuide/en/modules/portala=
pi.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=3D"center" fileref=3D"images/portalapi/Por=
talNodeEvent.png" format=3D"png"/>
+               <imagedata align=3D"center" fileref=3D"images/portalapi/Por=
talNodeEvent.png" format=3D"png" scalefit=3D"1"/>
             </imageobject>
             <caption>
                <para>The portal node event class hierarchy</para>


--===============1109069396435649634==--