JBoss-5 CR2 : log4j.jar missing from jbossall-client.jar man

[jaikiran]

Starting JBoss-5 CR2 jbossall-client.jar acts as a manifest-only jar file which points to various other client jars. However the Manifest.mf is missing the %JBOSS_HOME%\client\log4j.jar file. The readme too does not have a mention about this file:

This jar file contains a classpath reference to various client jar files used by jboss client applications.
....
The classpath includes the following files:

commons-logging.jar
concurrent.jar
ejb3-persistence.jar
hibernate-annotations.jar
jboss-aop-jdk50-client.jar
jboss-appclient.jar
jboss-aspect-jdk50-client.jar
jboss-client.jar
jboss-common-core.jar
jboss-deployers-client-spi.jar
jboss-deployers-client.jar
jboss-deployers-core-spi.jar
jboss-deployers-core.jar
jboss-deployment.jar
jboss-ejb3-common-client.jar
jboss-ejb3-core-client.jar
jboss-ejb3-ext-api.jar
jboss-ejb3-proxy-client.jar
jboss-ejb3-proxy-clustered-client.jar
jboss-ejb3-security-client.jar
jboss-ha-client.jar
jboss-ha-legacy-client.jar
jboss-iiop-client.jar
jboss-integration.jar
jboss-j2se.jar
jboss-javaee.jar
jboss-jsr77-client.jar
jboss-logging-jdk.jar
jboss-logging-log4j.jar
jboss-logging-spi.jar
jboss-main-client.jar
jboss-mdr.jar
jboss-messaging.jar
jboss-remoting.jar
jboss-security-spi.jar
jboss-serialization.jar
jboss-srp-client.jar
jboss-system-client.jar
jboss-system-jmx-client.jar
jbosscx-client.jar
jbosssx-as-client.jar
jbosssx-client.jar
jmx-client.jar
jmx-invoker-adaptor-client.jar
jnp-client.jar
slf4j-api.jar
slf4j-jboss-logging.jar
xmlsec.jar

Was this intentional to leave out the log4j.jar file? Without this jar file available, the logging on the client side never happens. I had to separately include this log4j.jar in the client classpath in addition to jbossall-client.jar. Is this intentional?

[alesj]

Probably this explains this a bit:
- http://lists.jboss.org/pipermail/jboss-development/2008-October/012663.html

[jaikiran]

Looks similar. And also looks like a hint that the log4j.jar was not intentionally left out :-)

[dimitris]

I looked at 5.0.0.Beta4 and 4.2.3.GA jbossall-client.jar and I don't think it includes the log4j classes. Or can you point to another version that included those?

[jaikiran]

You are right. I just tried an client application with 4.2.3 GA and 5.0 Beta4. Even those don't log anything until i specifically add the log4j.jar to the client classpath.

I now understand why i did not notice this earlier before CR2 - Till date i was always using Eclipse to run the client application and the log4j.jar was present in my default classpath and as a result i saw the logs on the client side. Its only during my recent testing that i switched to use the command prompt and specify the classpath explicity through the -classpath option:

java -classpath "%JBOSS_HOME%\client\jbossall-client.jar" ....

and that's when i noticed this behavior and incorrectly thought that it was because of the jbossall-client.jar changes. Apologies for wasting your time on this silly oversight.