From jboss-remoting-commits at lists.jboss.org Sat Sep 12 18:52:51 2009
Content-Type: multipart/mixed; boundary="===============2709484613359014236=="
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: r5463 -
remoting2/branches/2.x/docs/guide/en.
Date: Sat, 12 Sep 2009 18:52:50 -0400
Message-ID: <200909122252.n8CMqoIL021197@svn01.web.mwc.hst.phx2.redhat.com>
--===============2709484613359014236==
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 18:52:50 -0400 (Sat, 12 Sep 2009)
New Revision: 5463
Modified:
remoting2/branches/2.x/docs/guide/en/chap4.xml
Log:
JBREM-1151: Updated dependencies.
Modified: remoting2/branches/2.x/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.x/docs/guide/en/chap4.xml 2009-09-12 21:14:16 UTC =
(rev 5462)
+++ remoting2/branches/2.x/docs/guide/en/chap4.xml 2009-09-12 22:52:50 UTC =
(rev 5463)
@@ -9,7 +9,8 @@
=
jboss-remoting.jar - this bin=
ary
contains all the remoting classes. This is the only remoting jar that =
is
- needed to perform any remoting function within JBoss Remoting.
+ needed to perform any remoting function within JBoss Remoting. Of cou=
rse,
+ third party jars will be required.
=
Since some may want to better control size of the binary footpri=
nt
needed to use remoting, the remoting classes have been broken out into
@@ -82,71 +83,176 @@
functions.
=
- Thirdparty libraries
+ Third party libraries
=
This section covers which thirdparty jars are required based on
- the feature or transport to be used. Remember, whenever see
- jboss-remoting-XXX.jar mentioned, they can all be replaced with just=
the
+ the feature or transport to be used. Remember, any
+ jboss-remoting-XXX.jar can be replaced with just the
jboss-remoting.jar.
+ =
+ Table 1 gives the direct dependencies of the Remoting jars on
+ third party jars (and jboss-remoting-core.jar, in most cases). Tabl=
e 2
+ gives the transitive closure of Table 1.
=
- All remoting servers:
- jboss-remoting-core.jar, jboss-common.jar, jboss-jmx.jar,
- log4j.jar
+ 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.
=
- All remoting clients:
- jboss-remoting-core.jar, jboss-common.jar, jboss-jmx.jar,
- log4j.jar, concurrent.jar
+
+
+
=
- Note: concurrent.jar needed because of org.jboss.util.id.GUID =
used
- to create session id within Client
- (http://jira.jboss.com/jira/browse/JBREM-549)
+
+
+ jar
+ depends on
+
+
=
- 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 implementat=
ion
- library (or exclude it if using jdk 1.5 or higher, which has JMX
- implementation built in).
+
+
+ jboss-remoting-bisocket-client.jar:
+ concurrent.jar, jboss-common-core.jar, jboss-lo=
gging-spi.jar, jboss-remoting-core.jar, jboss-serialization.jar
+
+
+ jboss-remoting-bisocket.jar:
+ concurrent.jar, jboss-common-core.jar, jboss-lo=
gging-spi.jar, jboss-remoting-core.jar, jboss-serialization.jar
+
+
+ jboss-remoting-core.jar:
+ concurrent.jar, jboss-common-core.jar, jboss-j2=
se.jar, jboss-logging-spi.jar, jboss-remoting-detection.jar, jboss-serializ=
ation.jar, log4j.jar
+
=
+
+ jboss-remoting-detection.jar:
+ jboss-j2se.jar, jboss-logging-spi.jar, jboss-re=
moting-core.jar, jnpserver.jar, log4j.jar
+
=
+
+ jboss-remoting-http-client.jar:
+ jboss-common-core.jar, jboss-logging-spi.jar, j=
boss-remoting-core.jar
+
=
+
+ jboss-remoting-http.jar:
+ jboss-common-core.jar, jboss-logging-spi.jar, j=
boss-remoting-core.jar, jbossweb.jar
+
=
+
+ jboss-remoting-rmi.jar:
+ jboss-common-core.jar, jboss-logging-spi.jar, j=
boss-remoting-core.jar, jboss-serialization.jar
+
+
+ jboss-remoting-samples.jar:
+ jboss-common-core.jar, jboss-logging-log4j.jar,=
jboss-logging-spi.jar, jboss-remoting-bisocket-client.jar, jboss-remoting-=
core.jar, jboss-remoting-detection.jar, jboss-remoting.jar, jnpserver.jar, =
junit.jar, log4j.jar, servlet-api.jar
+
+
+ jboss-remoting-serialization.jar:
+ jboss-logging-spi.jar, jboss-remoting-core.jar,=
jboss-serialization.jar
+
+
+ jboss-remoting-servlet.jar:
+ jboss-logging-spi.jar, jboss-remoting-core.jar,=
servlet-api.jar
+
+
+ jboss-remoting-socket-client.jar:
+ concurrent.jar, jboss-common-core.jar, jboss-lo=
gging-spi.jar, jboss-remoting-core.jar
+
+
+ jboss-remoting-socket.jar:
+ concurrent.jar, jboss-common-core.jar, jboss-lo=
gging-spi.jar, jboss-remoting-core.jar, jboss-serialization.jar
+
+
+ jboss-remoting.jar:
+ concurrent.jar, jboss-common-core.jar, jboss-j2=
se.jar, jboss-logging-log4j.jar, jboss-logging-spi.jar, jboss-serialization=
.jar, jbossweb.jar, jnpserver.jar, junit.jar, log4j.jar, servlet-api.jar
+
+ =
+ =
+
+
+ =
+ =
+
+ Transitive closure of jar dependencies.
=
- Multicast detection:
- jboss-remoting-detection.jar, concurrent.jar,
- dom4j.jar
+
+
+
=
- JNDI detection:
- jboss-remoting-detection.jar, concurrent.jar, dom4j.jar, jnpserver.j=
ar
- (for jndi api classes)
+
+
+ jar
+ depends on
+
+
=
- The dom4j.jar for use of detection is required because using
- jboss-jmx.jar.
-
- Socket server:
- jboss-remoting-socket.jar
-
- Socket client:
- jboss-remoting-socket-client.jar
-
- HTTP server:
- jboss-remoting-http.jar, tomcat-coyote.jar, tomcat-util.jar,
- tomcat-http.jar, commons-logging-api.jar; alternatively, the tomcat =
jars
- can be replaced by jbossweb.jar
-
- Note: need tomcat-apr.jar (if using tomcat jars) and
- tcnative-1.dll/tcnative-1.so on system path to use APR based tomcat
- connector
+
+
+ jboss-remoting-bisocket-client.jar:
+ concurrent.jar, jboss-common-core.jar, jboss-j2=
se.jar, jboss-logging-spi.jar, jboss-remoting-core.jar, [jboss-remoting-det=
ection.jar], jboss-serialization.jar, [jnpserver.jar], log4j.jar, trove.jar=
+
+
+ jboss-remoting-bisocket.jar:
+ concurrent.jar, jboss-common-core.jar, jboss-j2=
se.jar, jboss-logging-spi.jar, jboss-remoting-core.jar, [jboss-remoting-det=
ection.jar], jboss-serialization.jar, [jnpserver.jar], log4j.jar, trove.jar=
+
+
+ jboss-remoting-core.jar:
+ concurrent.jar, jboss-common-core.jar, jboss-j2=
se.jar, jboss-logging-spi.jar, [jboss-remoting-detection.jar], jboss-serial=
ization.jar, [jnpserver.jar], log4j.jar, trove.jar
+
=
+
+ jboss-remoting-detection.jar:
+ concurrent.jar, jboss-common-core.jar, jboss-j2=
se.jar, jboss-logging-spi.jar, jboss-remoting-core.jar, jboss-serialization=
.jar, jnpserver.jar, log4j.jar, trove.jar
+
=
+
+ jboss-remoting-http-client.jar:
+ concurrent.jar, jboss-common-core.jar, jboss-j2=
se.jar, jboss-logging-spi.jar, jboss-remoting-core.jar, [jboss-remoting-det=
ection.jar], jboss-serialization.jar, [jnpserver.jar], log4j.jar, trove.jar=
+
=
+
+ jboss-remoting-http.jar:
+ concurrent.jar, jboss-common-core.jar, jboss-j2=
se.jar, jboss-logging-spi.jar, jboss-remoting-core.jar, [jboss-remoting-det=
ection.jar], jboss-serialization.jar, jbossweb.jar, [jnpserver.jar], log4j.=
jar, servlet-api.jar, trove.jar
+
+
+ jboss-remoting-rmi.jar:
+ concurrent.jar, jboss-common-core.jar, jboss-j2=
se.jar, jboss-logging-spi.jar, jboss-remoting-core.jar, [jboss-remoting-det=
ection.jar], jboss-serialization.jar, [jnpserver.jar], log4j.jar, trove.jar=
+
+
+ jboss-remoting-samples.jar:
+ concurrent.jar, jboss-common-core.jar, jboss-j2=
se.jar, jboss-logging-log4j.jar, jboss-logging-spi.jar, jboss-remoting-biso=
cket-client.jar, jboss-remoting-core.jar, [jboss-remoting-detection.jar], j=
boss-serialization.jar, [jnpserver.jar], junit.jar, log4j.jar, servlet-api=
.jar, trove.jar
+
+
+ jboss-remoting-serialization.jar:
+ concurrent.jar, jboss-common-core.jar, jboss-j2=
se.jar, jboss-logging-spi.jar, jboss-remoting-core.jar, [jboss-remoting-det=
ection.jar], jboss-serialization.jar, [jnpserver.jar], log4j.jar, trove.jar=
+
+
+ jboss-remoting-servlet.jar:
+ concurrent.jar, jboss-common-core.jar, jboss-j2=
se.jar, jboss-logging-spi.jar, jboss-remoting-core.jar, [jboss-remoting-det=
ection.jar], jboss-serialization.jar, [jnpserver.jar], log4j.jar, servlet-a=
pi.jar, trove.jar
+
+
+ jboss-remoting-socket-client.jar:
+ concurrent.jar, jboss-common-core.jar, jboss-j2=
se.jar, jboss-logging-spi.jar, jboss-remoting-core.jar, [jboss-remoting-det=
ection.jar], jboss-serialization.jar, [jnpserver.jar], log4j.jar, trove.jar=
+
+
+ jboss-remoting-socket.jar:
+ concurrent.jar, jboss-common-core.jar, jboss-j2=
se.jar, jboss-logging-spi.jar, jboss-remoting-core.jar, [jboss-remoting-det=
ection.jar], jboss-serialization.jar, [jnpserver.jar], log4j.jar, trove.jar=
+
+
+ jboss-remoting.jar:
+ concurrent.jar, jboss-common-core.jar, jboss-j2=
se.jar, jboss-logging-log4j.jar, jboss-logging-spi.jar, jboss-serialization=
.jar, jbossweb.jar, jnpserver.jar, junit.jar, log4j.jar, servlet-api.jar, t=
rove.jar
+
+ =
+ =
+
+
=
- HTTP client:
- jboss-remoting-http-client.jar
+ Notes.
+ =
+ 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.
=
- Servlet server:
- servlet-invoker.war (deployed in web container),
- jboss-remoting-servlet.jar
-
- Servlet client:
- jboss-remoting-http-client.jar
-
- RMI server and client:
- jboss-remoting-rmi.jar
-
- JBoss serialization:
- jboss-serialization.jar, trove.jar
\ No newline at end of file
--===============2709484613359014236==--