Hi, guys. How do I turn off all the wicket debug statements when running from a WAR file with Jetty? When I run un-WARed, it seems to pick up the log4j configuration (debug is off, info is on), but not when using a WAR file (debug is on, info is on).
I tried this using the wicket examples. I modified the Jetty config file to point to the WAR file and got the results I described. So, currently commons-logging.properties and log4j.properties are under WEB-INF/classes in the WAR file (which must not be right?). Of course, my next goal is to get my own logging statements properly configured, but I think that should be obvious once I get past this problem. Thanks, -Andy ------------------------------------------------------- This SF.Net email is sponsored by Yahoo. Introducing Yahoo! Search Developer Network - Create apps using Yahoo! Search APIs Find out how you can build Yahoo! directly into your own Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005 _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
