It didn't make sense to have a servlet do logging setup, since a) servlets are initialized pretty late and b) there could be multiple servlets.
Most of what I originally envisioned setupLogging() to do can be done using a log4j.properties file on the classpath. You can always subclass ApplicationServlet and override init() to put any application-specific logging setup in place that can't be expressed using log4j.properties. -- [EMAIL PROTECTED] http://tapestry.sf.net > Hello, > I am attempting to use the new 2.3 beta and I am wondering where I > should put code that I used to put in setupLogging(). > Also, where can I find a list of these API changes for each release ( I > assume the rationale and work around for the changes is posted there ). > > Thanks > > Luke Galea > Software Development > BlueCat <http://www.bluecatnetworks.com/> Networks > 905-762-5225 > > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
