Looks similar. And also looks like a hint that the log4j.jar was not intentionally left out :-)
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?
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.