[jboss-cvs] jboss-portal-docs/referenceGuide/en/modules ...

[Rali Genova]

  User: rgenova 
  Date: 06/07/12 23:09:33

  Modified:    referenceGuide/en/modules  clustering.xml
  Log:
  proof-reading clustering module
  
  Revision  Changes    Path
  1.8       +10 -12    jboss-portal-docs/referenceGuide/en/modules/clustering.xml
  
  (In the diff below, changes in quantity of whitespace are not shown.)
  
  Index: clustering.xml
  ===================================================================
  RCS file: /cvsroot/jboss/jboss-portal-docs/referenceGuide/en/modules/clustering.xml,v
  retrieving revision 1.7
  retrieving revision 1.8
  diff -u -b -r1.7 -r1.8
  --- clustering.xml	6 Jul 2006 20:38:17 -0000	1.7
  +++ clustering.xml	13 Jul 2006 03:09:32 -0000	1.8
  @@ -74,21 +74,19 @@
      </sect1>
      <sect1>
         <title>Considerations</title>
  -      <para>When you want to use JBoss Portal on a cluster there are a number items to respect :
  +      <para>When you want to run JBoss Portal on a cluster there are a few things to keep in mind:
         <itemizedlist>
  -         <listitem>Use the <emphasis role="bold">all</emphasis> application server configuration : the all configuration
  -         contains the clustering services that JBoss Portal leverages.</listitem>
  -         <listitem>All the portal instances have to use the same datasource : the database is used to store the the portal
  -         persistent state like pages. If you don't use a common database then you will see consitency problems.</listitem>
  +         <listitem>Deploy the portal under the <emphasis role="bold">all</emphasis> application server configuration as it contains the clustering services that JBoss Portal leverages.</listitem>
  +         <listitem>All the portal instances have to use the same datasource : the database is used to store the portal
  +         persistent state like pages. If you don't use a shared database then you will have consitency problems.</listitem>
         </itemizedlist></para>
      </sect1>
      <sect1>
         <title>Portlet Session Replication</title>
  -      <para>Web containers offers the capability to replication sessions of web applications. In the context of
  -      a portal using portlets the use case is different. In that context, the portal itself is a web application
  +      <para>Web containers offer the capability to replicate sessions of web applications. In the context of a portal using portlets the use case is different. The portal itself is a web application
         that benefits of web application session replication. We have to make the distinction between local or remote portlets :
            <itemizedlist>
  -            <listitem>Local portlets are web applications deployed in the same virtual machine than the portal
  +            <listitem>Local portlets are web applications deployed in the same virtual machine as the portal
               web application. At runtime the access to a portlet is done using the mechanism of request dispatching. The portlet
               session is actually a mere wrapper of the underlying http session of the web application in which the portlet
               is deployed.</listitem>
  @@ -102,7 +100,7 @@
            <listitem>Replicate only the portlet that requires it.</listitem>
            <listitem>Portal session replication is just web application replication and is very standard.</listitem>
         </itemizedlist>
  -      <para>It has also some limitation such has you can only replicate portlet scoped attributes of a portlet
  +      <para>There are also some limitation such has you can only replicate portlet scoped attributes of a portlet
            session. It means that any attribute scoped using application scope are not replicated.</para>
         <sect2>
            <title>JBoss Portal configuration</title>
  @@ -166,11 +164,11 @@
         </sect2>
         <sect2>
            <title>Limitations</title>
  -         <para>As said earlier this mechanism has advantages but has also two limitations</para>
  +         <para>As we noted above there are advantages as well as limitations to the clustering configuration</para>
            <itemizedlist>
               <listitem>You can only replicate portlet scoped attributes of a portlet. The main reason of this
  -            is to keep consistency with the session state. Indeed if accessing a portlet would trigger replication
  -            of application scoped attribute during the rendition of a page then another portlet on the same
  +            is to keep consistency with the session state. If accessing a portlet would trigger replication
  +            of application scoped attribute during the rendering of a page then another portlet on the same
               page could use this attribute for generating its markup. Then the state seen by this second portlet
               would not be the same according to the order in which the portlets of this page are rendered.</listitem>
               <listitem>Mutable objects need an explicit call to <emphasis>setAttribute(String name, Object value)</emphasis>