This looks like a bug that was already fixed in Seam, but I did not think that
the bug was in Seam 1.2.1. Are you sure you are really using 1.2.1.
Anyway, it can be solved by upgrading to a more recent log4j.
View the original post :
It has to be something to do with a bad log4j.jar version somewhere.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4067582#4067582
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4067582
I am using Seam 1.2.1GA
anonymous wrote : 12:29:06,046 INFO [ServletContextListener] Welcome to Seam
1.2.1
|
I dropped in the latest log4j.jar from JBoss 4.2.1GA build in front of the
client's classpath. Made no differences.
I am starting to doubt if it's Seam at all since I have Seam's
