[jboss-remoting-commits] JBoss Remoting SVN: r5462 - remoting2/branches/2.2/docs/guide/en.

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

Author: ron.sigal at jboss.com
Date: 2009-09-12 17:14:16 -0400 (Sat, 12 Sep 2009)
New Revision: 5462

Modified:
   remoting2/branches/2.2/docs/guide/en/chap4.xml
Log:
JBREM-1151: A few more changes.

Modified: remoting2/branches/2.2/docs/guide/en/chap4.xml
===================================================================
--- remoting2/branches/2.2/docs/guide/en/chap4.xml	2009-09-12 21:03:11 UTC (rev 5461)
+++ remoting2/branches/2.2/docs/guide/en/chap4.xml	2009-09-12 21:14:16 UTC (rev 5462)
@@ -98,6 +98,12 @@
       third party jars (and jboss-remoting-core.jar, in most cases).  Table 2
       gives the transitive closure of Table 1.</para>
 
+      <para>The information in Tables 1 and 2 was derived with the use of the
+      extremely useful <emphasis role="bold">Tattletale</emphasis> tool,
+      available on the jboss.org website:
+      <ulink url="http://www.jboss.org/tattletale">
+      http://www.jboss.org/tattletale</ulink></para>
+      
       <table frame="all" id="JarDependencyTable" xreflabel="Table 1">
         <title>Jar dependencies.</title>
 
@@ -253,28 +259,28 @@
       
       <para><emphasis role="bold">Notes.</emphasis></para>
       
-      <para>1. jboss-common.jar needs commons-httpclient.jar, which explains
+      <para>1. jboss-remoting-core contains the transporter classes, and some of those
+      need jboss-remoting-detection.jar, which explains the proliferation of
+      jboss-remoting-detection.jar in Table 2.  If transporters are not used,
+      then jboss-remoting-detection.jar can be omitted.  Moreover, JNDI detection
+      requires jnpserver.jar, so that, if transporters are not used, jnpserver.jar
+      can be omitted.</para>
+      
+      <para>2. jboss-common.jar needs commons-httpclient.jar, which explains
       the transitive dependency of all Remoting jars on commons-httpclient.jar.
       Also, commons-httpclient.jar needs commons-logging-api.jar.</para>
 
-      <para>2. Remoting requires the use of JMX classes. It does not require the
+      <para>3. Remoting requires the use of JMX classes. It does not require the
       JBoss implementation (jboss-jmx.jar) of JMX in order to function
       correctly, so can replace jboss-jmx.jar with another JMX implementation
       library (or exclude it if using jdk 1.5 or higher, which has JMX
       implementation built in).</para>
       
-      <para>3. Multicast detection requires jboss-remoting-detection.jar, concurrent.jar,
+      <para>4. Multicast detection requires jboss-remoting-detection.jar, concurrent.jar,
       dom4j.jar. JNDI detection: requires
       jboss-remoting-detection.jar, concurrent.jar, dom4j.jar, jnpserver.jar
       (for jndi api classes).  dom4j.jar for use of detection is required by
       jboss-jmx.jar.</para>
-      
-      <para>4. jboss-remoting-core contains the transporter classes, and some of those
-      need jboss-remoting-detection.jar, which explains the proliferation of
-      jboss-remoting-detection.jar in Table 2.  If transporters are not used,
-      then jboss-remoting-detection.jar can be omitted.  Moreover, JNDI detection
-      requires jnpserver.jar, so that, if transporters are not used, jnpserver.jar
-      can be omitted.</para>
 
     </section>
   </chapter>
\ No newline at end of file