For the work that I do, logging to the server.log is no problem for me, so I have not tried to separate the logging out to other files.
The main reason for my suggestion regarding the commons logging file location was the possibility that you are running into a class loader issue, which seems to be confirmed by your latest message. But after thinking about it some more, maybe I should have suggested that you put the commons logging jar file into your WEB-INF/lib directory. By the way, one way of debugging a cloass loader issue is add the -verbose:class JVM option to the command line. The JVM will then tell you for each class loaded what jar file it came from. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3930181#3930181 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3930181 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
