From jboss-remoting-commits at lists.jboss.org Sat Sep 12 17:14:16 2009 Content-Type: multipart/mixed; boundary="===============5250512276468443924==" MIME-Version: 1.0 From: jboss-remoting-commits at lists.jboss.org To: jboss-remoting-commits at lists.jboss.org Subject: [jboss-remoting-commits] JBoss Remoting SVN: r5462 - remoting2/branches/2.2/docs/guide/en. Date: Sat, 12 Sep 2009 17:14:16 -0400 Message-ID: <200909122114.n8CLEGgo000306@svn01.web.mwc.hst.phx2.redhat.com> --===============5250512276468443924== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Author: ron.sigal(a)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 =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 --- 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). Tabl= e 2 gives the transitive closure of Table 1. = + The information in Tables 1 and 2 was derived with the use of = the + extremely useful Tattletale tool, + available on the jboss.org website: + + http://www.jboss.org/tattletale + = Jar dependencies. = @@ -253,28 +259,28 @@ = Notes. = - 1. jboss-common.jar needs commons-httpclient.jar, which explai= ns + 1. jboss-remoting-core contains the transporter classes, and s= ome of those + need jboss-remoting-detection.jar, which explains the proliferation = of + jboss-remoting-detection.jar in Table 2. If transporters are not us= ed, + then jboss-remoting-detection.jar can be omitted. Moreover, JNDI de= tection + requires jnpserver.jar, so that, if transporters are not used, jnpse= rver.jar + can be omitted. + = + 2. jboss-common.jar needs commons-httpclient.jar, which explai= ns the transitive dependency of all Remoting jars on commons-httpclient= .jar. Also, commons-httpclient.jar needs commons-logging-api.jar. = - 2. Remoting requires the use of JMX classes. It does not requi= re the + 3. Remoting requires the use of JMX classes. It does not requi= re the JBoss implementation (jboss-jmx.jar) of JMX in order to function correctly, so can replace jboss-jmx.jar with another JMX implementat= ion library (or exclude it if using jdk 1.5 or higher, which has JMX implementation built in). = - 3. Multicast detection requires jboss-remoting-detection.jar, = concurrent.jar, + 4. Multicast detection requires jboss-remoting-detection.jar, = concurrent.jar, dom4j.jar. JNDI detection: requires jboss-remoting-detection.jar, concurrent.jar, dom4j.jar, jnpserver.j= ar (for jndi api classes). dom4j.jar for use of detection is required = by jboss-jmx.jar. - = - 4. jboss-remoting-core contains the transporter classes, and s= ome of those - need jboss-remoting-detection.jar, which explains the proliferation = of - jboss-remoting-detection.jar in Table 2. If transporters are not us= ed, - then jboss-remoting-detection.jar can be omitted. Moreover, JNDI de= tection - requires jnpserver.jar, so that, if transporters are not used, jnpse= rver.jar - can be omitted. = \ No newline at end of file --===============5250512276468443924==--