Hi, I figured out myself. Here is the explanation if someone gets the same problem. There is a new package under deploy directory called ebxmlrr-service.sar. Apparently, this package contains commons-logging.properties file that specifies NoOpLog as an implementation for the logger that stops all the logging from jakarta commons. The solution is to create commons-logging.properties file and drop it under the server/[server name]/lib directory with the following contents:
org.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4JLogger This is, of course, if you want to use log4j as an underlying mechanism. Thanks, Misak View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3852958#3852958 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3852958 ------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
