[jboss-jira] [JBoss JIRA] Commented: (JBREM-311) need required library matrix

[Tom Elrod (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBREM-311?page=comments#action_12339855 ] 
            
Tom  Elrod commented on JBREM-311:
----------------------------------

The following covers which remoting jars and thirdparty jars will be needed depending on what features of remoting will be used.

Remoting jars:

jboss-remoting.jar (734K) - this binary contains all the remoting classes.  This is the only remoting jar that is needed to perform any remoting funtion within JBoss Remoting.

Since some may want to better control size of the binary footprint needed to use remoting, the remoting classes have been broken out into multiple remoting binaries based on their function.  There are three categories of these binaries; core, detection, and transport.

core:

jboss-remoting-core.jar (204K) - contains all the core remoting classes needed for remoting to function.  If not using jboss-remoting.jar, then jboss-remoting.core.jar will be required.

detection:

jboss-remoting-detection (40K) - contains all the remoting classes needed to perform automatic discovery of remoting servers.  It includes both the jndi and multicast detector classes as well as the network registry classes.

transport:

jboss-remoting-socket.jar (41K) - contains all the classes needed for the socket and sslsocket transports to function as both a client and a server.
jboss-remoting-socket-client.jar (21K) - contains all the classes needed for the socket and sslsocket transports to function as a client only.  This means will not be able to perform any push callbacks or sending of streams using this jar.
jboss-remoting-http.jar (59K) - contains all the classes needed for the http and https transports to function as a client and a server.
jboss-remoting-http-client.jar (18K) - contains all the classes needed for the http, https, servlet, and sslservlet transports to function as a client only.  This means will not be able to perform any push callbacks or sending of streams using this jar.
jboss-remoting-servlet.jar (10K) - contains all the classes needed for the servlet or sslservlet transports to function as a server only (also requires servlet-invoker.war be deployed within web container as well)
jboss-remoting-rmi.jar (20K) - contains all the classes needed for the rmi and sslrmi transports to function as a client and a server.
jboss-remoting-multiplex.jar (126K) - 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.



Thirdparty jars:

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 jboss-remoting.jar.

all remoting servers:
- jboss-remoting-core.jar
- jboss-common.jar
- jboss-jmx.jar
- log4j.jar

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)

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).

multicast detection
- jboss-remoting-detection.jar
- concurrent.jar
- dom4j.jar

jndi detection
- jboss-remoting-detection.jar
- concurrent.jar
- dom4j.jar
- jnpserver.jar (for jndi api classes)

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
- 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


if use JBoss Serialization, will need to include jboss-serialization.jar and trove.jar





> need required library matrix
> ----------------------------
>
>                 Key: JBREM-311
>                 URL: http://jira.jboss.com/jira/browse/JBREM-311
>             Project: JBoss Remoting
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: general
>    Affects Versions: 1.4.0 final
>            Reporter: Tom  Elrod
>         Assigned To: Ron Sigal
>            Priority: Minor
>             Fix For: 2.0.0.CR1 (Boon)
>
>
> Since remoting has been changed to load needed libraries when actually needed (not statically upon startup), do not know exactly which jars are needed on classpath until runtime.  
> Therefore, need a matrix that shows exactly which jars are needed for each of the different transports and features.  For example, if using http trnasport, need the tomcat jars.  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira