[jboss-cvs] JBossAS SVN: r105462 - projects/docs/enterprise/EAP/trunk/5.x/Seam_Reference_Guide/en-US.

[jboss-cvs-commits at lists.jboss.org]

Author: misty at redhat.com
Date: 2010-06-01 02:31:07 -0400 (Tue, 01 Jun 2010)
New Revision: 105462

Modified:
   projects/docs/enterprise/EAP/trunk/5.x/Seam_Reference_Guide/en-US/Clustering_EJBPassivation.xml
Log:
JBPAPP-4387


Modified: projects/docs/enterprise/EAP/trunk/5.x/Seam_Reference_Guide/en-US/Clustering_EJBPassivation.xml
===================================================================
--- projects/docs/enterprise/EAP/trunk/5.x/Seam_Reference_Guide/en-US/Clustering_EJBPassivation.xml	2010-06-01 06:29:28 UTC (rev 105461)
+++ projects/docs/enterprise/EAP/trunk/5.x/Seam_Reference_Guide/en-US/Clustering_EJBPassivation.xml	2010-06-01 06:31:07 UTC (rev 105462)
@@ -72,12 +72,12 @@
    <para>
       If your nodes are on different machines that run Red Hat Enterpise Linux or Fedora, they may not acknowledge each other automatically. JBoss AS clustering relies on the UDP (User Datagram Protocol) multi-casting provided by jGroups. The SELinux configuration that ships with Red Hat Enterprise Linux and Fedora blocks these packets by default. To allow the packets, modify the <literal>iptables</literal> rules (as root). The following commands apply to an IP address that matches <literal>192.168.1.x</literal>:
    </para>
-   <programlisting>
+   <screen>
   /sbin/iptables -I RH-Firewall-1-INPUT 5 -p udp -d 224.0.0.0/4 -j ACCEPT
   /sbin/iptables -I RH-Firewall-1-INPUT 9 -p udp -s 192.168.1.0/24 -j ACCEPT
   /sbin/iptables -I RH-Firewall-1-INPUT 10 -p tcp -s 192.168.1.0/24 -j ACCEPT
   /etc/init.d/iptables save
-   </programlisting>
+   </screen>
 </note>
 <note>
    <title>A note about Stateful Session Beans</title>
@@ -133,7 +133,7 @@
          <para>
             Start the master JBoss AS instance on the first IP:
          </para>
-         <programlisting>  ./bin/run.sh -c all -b 192.168.1.2</programlisting>
+         <screen>  ./bin/run.sh -c all -b 192.168.1.2</screen>
          <para>
             The log should report one cluster member and zero other members.
          </para>
@@ -147,7 +147,7 @@
          <para>
             Start the slave JBoss AS instance on the second IP:
          </para>
-         <programlisting>  ./bin/run.sh -c all -b 192.168.1.3</programlisting>
+         <screen>  ./bin/run.sh -c all -b 192.168.1.3</screen>
          <para>
             The log should report two cluster members and one other member. It should also show the state being retrieved from the master instance.
          </para>
@@ -210,7 +210,7 @@
 
             <para>
                You can watch objects passivate and activate by creating a session- or conversation-scoped Seam component and implementing the appropriate life-cycle methods. You can use methods from the <literal>HttpSessionActivationListener</literal> interface (which is automatically registered on all non-EJB components):</para>
-<programlisting role="JAVA"><![CDATA[public void sessionWillPassivate(HttpSessionEvent e);
+<programlisting language="Java" role="JAVA"><![CDATA[public void sessionWillPassivate(HttpSessionEvent e);
 public void sessionDidActivate(HttpSessionEvent e);
 ]]></programlisting>
             <para>
@@ -235,7 +235,7 @@
             The <literal>ManagedEntityInterceptor</literal> (MEI) is an optional interceptor in Seam. When enabled, it is applied to conversation-scoped components. To enable the MEI, set <varname>distributable</varname> to <literal>true</literal> on the <literal>org.jboss.seam.init.core</literal> component. You can also add or update the following component declaration in your <filename>components.xml</filename> file:
         </para>
 
-<programlisting role="XML"><![CDATA[<core:init distributable="true"/>
+<programlisting language="XML" role="XML"><![CDATA[<core:init distributable="true"/>
 ]]></programlisting>
             
         <para>