Hi Martin, I tried but I should have missed one because it was not working with my ear, I will test it again on Monday, but anyway you probably saved my week-end! ;) I also tried with a simple wicket quickstart and of course, it did not work because of the properties file. So there will be another question : how will/can you handle the quickstart for this particular situation?
Thanks again and best regards, Sebastien. On Fri, Aug 8, 2014 at 6:47 PM, Martin Grigorov <mgrigo...@apache.org> wrote: > Sebastien, > > Remove any log4j.properties from your .war/.ear/.jar files. > This fixed it here. > > Martin Grigorov > Wicket Training and Consulting > https://twitter.com/mtgrigorov > > > On Fri, Aug 8, 2014 at 6:41 PM, Sebastien <seb...@gmail.com> wrote: > > > Hi David, > > > > Actually, I already receive jboss's logs (org.jboss, org.wildfly, > > javax.enterprise, org.hibernate) in the console (if it was not clear)... > > > > Yes, I did read the links you mentioned (even if lines like " > > /subsystem=logging/logger=com.your.category:add" does absolutely means > > nothing for me, I don't know where I am suppose to write these kind of > > lines. But not sure if it's important)... > > > > Interesting point however: if I take a wildfly quickstart [1] and put an > > slf4j or a log4j logger, it works immediately (without any > > configuration!)... > > > > Thanks again & have a good WE, > > Sebastien. > > > > [1] https://github.com/wildfly/quickstart > > > > > > On Fri, Aug 8, 2014 at 5:47 PM, David Beer <david.m.b...@gmail.com> > wrote: > > > > > Hi Sebastien > > > > > > You get no log messages at to standalone/log/server.log file. If not I > > > would suggest posting to the Wildfly forum or taking a visit to there > IRC > > > channel. The server.log file should receive all logging unless > configured > > > not to. I assume you have seen this document > > > https://docs.jboss.org/author/display/WFLY8/Logging+Configuration or > > this > > > > > > > > > https://docs.jboss.org/author/display/WFLY8/How+To#HowTo-HowdoIuselog4j.propertiesorlog4j.xmlinsteadofusingtheloggingsubsystemconfiguration%3F > > > > > > To me it would sound like a Wildfly or JBoss issue. > > > > > > > > >
