Il 26/01/2013 20:42, Lukasz Lenart ha scritto:
2013/1/26 fusillator <fusilla...@gmail.com>:
So it seems that the struts framework use strightly log4j too, ignoring the
container configuration, doesn't it?
Nope, if so it's a bug. S2 will try to use SLF4J (with new release),
then commons-logging (which mostly means Log4j) and at the end JDK
logging.
https://svn.apache.org/repos/asf/struts/struts2/trunk/xwork-core/src/main/java/com/opensymphony/xwork2/util/logging/LoggerFactory.java
Regards
It was my mistake.
in my case the tomcat default logger is juli and it doesn't implement the
commons logging interface, so the tomcat loaders can't use it and provide the
log4j library in web-app.
I erroneusly considered that tomcat-juli was a common-logging implementator, so
I didn't get why the system loader didn't load it before using the web-app lib.
Now it seems all correct...
Thank for the help
Best regards.
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
For additional commands, e-mail: user-h...@struts.apache.org