Nah, you are talking about very old Cayenne. 3.2M1 does not interfere with logging settings, except for requiring commons-logging.jar to be there.
jar tvf cayenne-server-3.2M1.jar |grep properties 931 Sun Jul 07 19:55:24 FET 2013 org/apache/cayenne/cayenne-strings.properties 117 Sun Jul 07 19:55:34 FET 2013 META-INF/maven/org.apache.cayenne/cayenne-server/pom.properties Though taking control of your own logging setup at the application level is certainly a very good idea. Andrus On Dec 3, 2013, at 4:26 PM, Christian Grobmeier <[email protected]> wrote: > When I recall correctly Cayenne takes it's own log4j.properties when nothing > is given. > > You could try to create your own log4j confiugraiton like that: > > log4j.logger.org.apache.cayenne=INFO > log4j.category.org.apache.struts2=INFO > log4j.category.org.apache=INFO > log4j.category.com.opensymphony.xwork2.=INFO > > > > On 3 Dec 2013, at 14:12, jotpe wrote: > >> Hello list, >> >> I'm getting started with cayenne >> 3.2M1<http://cayenne.apache.org/2013/07/cayenne-32m1-released.html>. >> I use it in a tomcat webapplication together with the webapplication >> framework struts2. When i add the cayenne jar and use or-mapper in jsp's >> the sublibrary from struts2 "freemarker" changes it's loglevel to debug and >> floods me with tons of messages. Doesnt matter what is i configure about >> the loglevel in struts it doenst change... >> >> Without cayenne freemarker logs only with info level. >> >> Does anybody know how to solve this? >> >> Best regards, Johannes > > > --- > http://www.grobmeier.de > @grobmeier > GPG: 0xA5CC90DB >
