Much has been said about this issue both on Struts 2.1 migration Wiki page and
previous emails on this subject on how to turn them off by putting a new limit
category in log4j.xml.
Some folks ,like me, do not use log4j and use only apache logging
[apache-logging-xxx.jar]. Is there any other way, like setting a constant in
struts.xml that can kill those darn messages at the application level.
I have managed to turn them off by setting filters at the server level but this
means all struts applications on the server would have theirs filtered and
other S2 application owners on the same server may not consider those messages
darn annoying after all.
__________________________________________________________________
Looking for the perfect gift? Give the gift of Flickr!
http://www.flickr.com/gift/
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
For additional commands, e-mail: user-h...@struts.apache.org
