From jboss-remoting-commits at lists.jboss.org Sat Sep 12 17:03:11 2009
Content-Type: multipart/mixed; boundary="===============0980519850849670337=="
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: r5461 -
remoting2/branches/2.2/docs/guide/en.
Date: Sat, 12 Sep 2009 17:03:11 -0400
Message-ID: <200909122103.n8CL3B1m030041@svn01.web.mwc.hst.phx2.redhat.com>
--===============0980519850849670337==
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:03:11 -0400 (Sat, 12 Sep 2009)
New Revision: 5461
Modified:
remoting2/branches/2.2/docs/guide/en/chap4.xml
Log:
JBREM-1151: Updated dependencies.
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 16:27:21 UTC =
(rev 5460)
+++ remoting2/branches/2.2/docs/guide/en/chap4.xml 2009-09-12 21:03:11 UTC =
(rev 5461)
@@ -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
@@ -63,8 +64,7 @@
=
jboss-remoting-multiplex.jar -
contains all the classes needed for the multiplex and sslmultiplex
- transports to function as a client and a server. Use of this jar also
- requires jboss-remoting-socket.jar be on classpath as well.
+ transports to function as a client and a server.
=
jboss-remoting-bisocket.jar -
contains all the classes needed for the bisocket and sslbisocket trans=
ports
@@ -87,72 +87,194 @@
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
+
+ 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-remoting-bisocket-client.jar:
+ concurrent.jar, jboss-common.jar, jboss-remotin=
g-core.jar, jboss-serialization.jar
+
+
+ jboss-remoting-bisocket.jar:
+ concurrent.jar, jboss-common.jar, jboss-remotin=
g-core.jar, jboss-serialization.jar
+
+
+ jboss-remoting-core.jar:
+ concurrent.jar, jboss-common.jar, jboss-jmx.jar=
, jboss-serialization.jar, log4j.jar, saxon.jar
+
=
+
+ jboss-remoting-detection.jar:
+ jboss-common.jar, jboss-jmx.jar, jboss-remoting=
-core.jar, jnpserver.jar, log4j.jar, saxon.jar
+
=
+
+ jboss-remoting-http-client.jar:
+ jboss-common.jar, jboss-remoting-core.jar
+
=
+
+ jboss-remoting-http.jar:
+ commons-httpclient.jar, jboss-common.jar, jboss=
-jmx.jar, jboss-remoting-core.jar, tomcat-coyote.jar, tomcat-util.jar
+
=
+
+ jboss-remoting-multiplex.jar:
+ concurrent.jar, jboss-common.jar, jboss-jmx.jar=
, jboss-remoting-core.jar, jboss-serialization.jar, log4j.jar
+
+
+ jboss-remoting-rmi.jar:
+ jboss-common.jar, jboss-remoting-core.jar
+
+
+ jboss-remoting-samples.jar:
+ dom4j.jar, jboss-common.jar, jboss-jmx.jar, jbo=
ss-remoting-core.jar, jboss-remoting-detection.jar, jboss-remoting-multiple=
x.jar, jnpserver.jar, junit.jar, saxon.jar, servlet-api.jar
+
+
+ jboss-remoting-serialization.jar:
+ jboss-common.jar, jboss-remoting-core.jar, jbos=
s-serialization.jar
+
+
+ jboss-remoting-servlet.jar:
+ jboss-common.jar, jboss-remoting-core.jar, serv=
let-api.jar
+
+
+ jboss-remoting-socket-client.jar:
+ concurrent.jar, jboss-common.jar, jboss-remotin=
g-core.jar
+
+
+ jboss-remoting-socket.jar:
+ concurrent.jar, jboss-common.jar, jboss-remotin=
g-core.jar, jboss-serialization.jar
+
+
+ jboss-remoting.jar:
+ commons-httpclient.jar, concurrent.jar, dom4j.j=
ar, jboss-common.jar, jboss-jmx.jar, jboss-serialization.jar, jnpserver.jar=
, junit.jar, log4j.jar, saxon.jar, servlet-api.jar, tomcat-coyote.jar, tomc=
at-util.jar
+
+ =
+ =
+
+
+ =
+ =
+
+ Transitive closure of jar dependencies.
+
+
+
+
+
+
+
+ jar
+ depends on
+
+
+
+
+
+ jboss-remoting-bisocket-client.jar:
+ commons-httpclient.jar, commons-logging-api.jar=
, concurrent.jar, dom4j.jar, jboss-common.jar, jboss-jmx.jar, jboss-remotin=
g-core.jar, [jboss-remoting-detection.jar], jboss-serialization.jar, [jnpse=
rver.jar], log4j.jar, trove.jar
+
+
+ jboss-remoting-bisocket.jar:
+ commons-httpclient.jar, commons-logging-api.jar=
, concurrent.jar, dom4j.jar, jboss-common.jar, jboss-jmx.jar, jboss-remotin=
g-core.jar, [jboss-remoting-detection.jar], jboss-serialization.jar, [jnpse=
rver.jar], log4j.jar, trove.jar
+
+
+ jboss-remoting-core.jar:
+ commons-httpclient.jar, commons-logging-api.jar=
, concurrent.jar, dom4j.jar, jboss-common.jar, jboss-jmx.jar, [jboss-remoti=
ng-detection.jar], jboss-serialization.jar, [jnpserver.jar], log4j.jar, tro=
ve.jar
+
=
+
+ jboss-remoting-detection.jar:
+ commons-httpclient.jar, commons-logging-api.jar=
, concurrent.jar, dom4j.jar, jboss-common.jar, jboss-jmx.jar, jboss-remotin=
g-core.jar, jboss-serialization.jar, jnpserver.jar, log4j.jar, trove.jar
+
=
+
+ jboss-remoting-http-client.jar:
+ commons-httpclient.jar, commons-logging-api.jar=
, concurrent.jar, dom4j.jar, jboss-common.jar, jboss-jmx.jar, jboss-remotin=
g-core.jar, [jboss-remoting-detection.jar], jboss-serialization.jar, [jnpse=
rver.jar], log4j.jar
+
=
+
+ jboss-remoting-http.jar:
+ commons-httpclient.jar, commons-logging-api.jar=
, concurrent.jar, dom4j.jar, jboss-common.jar, jboss-jmx.jar, jboss-remotin=
g-core.jar, [jboss-remoting-detection.jar], jboss-serialization.jar, [jnpse=
rver.jar], log4j.jar, trove.jar
+
+
+ jboss-remoting-multiplex.jar:
+ commons-httpclient.jar, commons-logging-api.jar=
, concurrent.jar, dom4j.jar, jboss-common.jar, jboss-jmx.jar, jboss-remotin=
g-core.jar, [jboss-remoting-detection.jar], jboss-serialization.jar, [jnpse=
rver.jar], log4j.jar, trove.jar
+
+
+ jboss-remoting-rmi.jar:
+ commons-httpclient.jar, commons-logging-api.jar=
, concurrent.jar, dom4j.jar, jboss-common.jar, jboss-jmx.jar, jboss-remotin=
g-core.jar, [jboss-remoting-detection.jar], jboss-serialization.jar, [jnpse=
rver.jar], log4j.jar, trove.jar
+
+
+ jboss-remoting-samples.jar:
+ commons-httpclient.jar, commons-logging-api.jar=
, concurrent.jar, dom4j.jar, jboss-common.jar, jboss-jmx.jar, jboss-remotin=
g-core.jar, jboss-remoting-detection.jar, jboss-remoting-multiplex.jar, jbo=
ss-serialization.jar, jnpserver.jar, junit.jar, log4j.jar, servlet-api.jar,=
trove.jar
+
+
+ jboss-remoting-serialization.jar:
+ commons-httpclient.jar, commons-logging-api.jar=
, concurrent.jar, dom4j.jar, jboss-common.jar, jboss-jmx.jar, jboss-remotin=
g-core.jar, [jboss-remoting-detection.jar], jboss-serialization.jar, [jnpse=
rver.jar], log4j.jar, trove.jar
+
+
+ jboss-remoting-servlet.jar:
+ commons-httpclient.jar, commons-logging-api.jar=
, concurrent.jar, dom4j.jar, jboss-common.jar, jboss-jmx.jar, jboss-remotin=
g-core.jar, [jboss-remoting-detection.jar], jboss-serialization.jar, [jnpse=
rver.jar], log4j.jar, servlet-api.jar, trove.jar
+
+
+ jboss-remoting-socket-client.jar:
+ commons-httpclient.jar, commons-logging-api.jar=
, concurrent.jar, dom4j.jar, jboss-common.jar, jboss-jmx.jar, jboss-remotin=
g-core.jar, [jboss-remoting-detection.jar], jboss-serialization.jar, [jnpse=
rver.jar], log4j.jar, trove.jar
+
+
+ jboss-remoting-socket.jar:
+ commons-httpclient.jar, commons-logging-api.jar=
, concurrent.jar, dom4j.jar, jboss-common.jar, jboss-jmx.jar, jboss-remotin=
g-core.jar, [jboss-remoting-detection.jar], jboss-serialization.jar, [jnpse=
rver.jar], log4j.jar, trove.jar
+
+
+ jboss-remoting.jar:
+ commons-httpclient.jar, commons-logging-api.jar=
, concurrent.jar, dom4j.jar, jboss-common.jar, jboss-jmx.jar, jboss-remotin=
g-detection.jar, jboss-serialization.jar, jnpserver.jar, junit.jar, log4j.j=
ar, servlet-api.jar, tomcat-apr.jar, tomcat-coyote.jar, tomcat-util.jar, tr=
ove.jar
+
+ =
+ =
+
+
+ =
+ Notes.
+ =
+ 1. 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
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).
-
- Multicast detection:
- jboss-remoting-detection.jar, concurrent.jar,
- dom4j.jar
-
- JNDI detection:
+ =
+ 3. 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)
-
- The dom4j.jar for use of detection is required because using
+ (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.
=
- 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,
- commons-logging-api.jar, tomcat-http.jar
-
- Note: need tomcat-apr.jar and tcnative-1.dll/tcnative-1.so on
- system path if want to use APR based tomcat connector
-
- HTTP client:
- jboss-remoting-http-client.jar
-
- 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
-
- Multiplex server and client:
- jboss-remoting-socket.jar, jboss-remoting-multiplex.jar
-
- JBoss serialization:
- jboss-serialization.jar, trove.jar
\ No newline at end of file
--===============0980519850849670337==--