Thanks,
Using only the package:
org.springframework.beans.factory.level=WARNING
to define the level worked really well.
Regards,
Edson.
Em 20/10/2010 14:54, Jason Britton escreveu:
Have you tried being less than class specific in your log level assignment?
Instead of
org.springframewor
Have you tried being less than class specific in your log level assignment?
Instead of
org.springframework.beans.factory.config.FieldRetrievingFactoryBean.level =
WARNING
org.springframework.beans.factory.support.DefaultListableBeanFactory.level =
WARNING
org.springframework.beans.factory.xml.XmlB
By "It works" I want to mean, some changes works (like the filename),
but the specific filters does not.
Please advise.
Edson.
Em 19/10/2010 21:04, Edson Carlos Ericksson Richter escreveu:
It works:
"file:///C:/Users/Edson/.netbeans/6.9/apache-tomcat-6.0.26_base/logs/somethingelse.201
It works:
"file:///C:/Users/Edson/.netbeans/6.9/apache-tomcat-6.0.26_base/logs/somethingelse.2010-10-19.log"
(I'm running Tomcat from inside NetBeans, in Windows platform - I have
also similar configuration in Ubuntu Server 10.10 with Tomcat alone).
Edson.
Em 19/10/2010 20:43, Jason Brit
Just for your sanity, to make sure there are no other logging.properties
files in your classpath, change the prefix for your FileHandler to something
other than catalina so you can be sure this logging.properties file is the
one being used for your logging config. If your prefix remains catalina..
Dear all,
I've already spent lot's of time trying to make some Spring Framework
messages go away from my log, without success. My last configuration is:
/** Begin of file **/
handlers = 1catalina.org.apache.juli.FileHandler,
2localhost.org.apache.juli.FileHandler,
3manager.org.apache.juli.F
