I guess he's talking of its current log4j setup which logs to stdout __ Cedric Gatay (@Cedric_Gatay <http://twitter.com/Cedric_Gatay>) http://code-troopers.com | http://www.bloggure.info | http://cedric.gatay.fr
On Wed, Aug 7, 2013 at 10:11 AM, Martin Grigorov <mgrigo...@apache.org>wrote: > On Wed, Aug 7, 2013 at 10:07 AM, Jens Jahnke <jan0...@gmx.net> wrote: > > > Hi, > > > > On Tue, 6 Aug 2013 15:11:34 -0400 > > Paul Bors <p...@bors.ws> wrote: > > > > PB> Isn't Log4J shipped with the quick-start? > > PB> > > PB> Create yourself a quick-start and analyze it: > > PB> http://wicket.apache.org/start/quickstart.html > > PB> > > PB> PS: You can also check the initialization related topics as well as > > PB> your first stop for Wicket's doc via the Wicket Free Guide at: > > PB> http://wicket.apache.org/learn/books/freeguide.html > > > > thanks for the information, the freeguide rocks. > > > > But actually I found the solution in wicket in action. :) > > > > Nonetheless it only logs to stdout but I guess thats a log4j question. > > > > What do you mean that it logs to stdout ? > There is no usage of System.out/err in Wicket. The RequestLogger uses > SLF4J. > Your question is really a log4j question (if you use slf4j-log4j as > backend). > > > > > > Regards, > > > > Jens > > > > -- > > 07. Ernting 2013, 10:04 > > Homepage : http://www.jan0sch.de > > > > In order to live free and happily, you must sacrifice boredom. > > It is not always an easy sacrifice. > > >
