On 07/08/06, Pierre-Yves Saumont <[EMAIL PROTECTED]> wrote:

> Surely enabling debug for wicket.util.resource.Resource would help. I
> put a property file in the classpath with the following line :
> log4j.logger.wicket.util.resource=DEBUG
> but it doesn't change anything.
> Does any one has an idea of what markup element is missing or how to get
> log4j to work ?

Wicket uses commons-logging internally, so it should just be a matter
of a log4j.properties, but you might want to try also having a
commons-logging.properties with a
inside too.

(Personally, I'm now tending to go with clogging redirected to Simple
Logging (https://simple-log.dev.java.net/) just to be sure I don't get
issues with 'rogue' log4j configs being found where I don't expect

Download Wicket 1.2.1 now! - http://wicketframework.org

Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
Wicket-user mailing list

Reply via email to