There was no slf4j or log4j2 when we chose our logging system. But even today, I'd still say commons logging makes the most sense for a framework like Cayenne since every other logging system works well with it, which allows the end-user to decide which logging system they want to select for their own applications.
On Tue, Dec 3, 2013 at 9:30 AM, Christian Grobmeier <[email protected]> wrote: > On 3 Dec 2013, at 14:52, Mike Kienenberger wrote: > >> Everyone has their favorite logger. >> >> The commons logging api is supported by all of them, sometimes without >> even needing the actual commons logging jars, as I'm sure you already >> know. :-) > > > The log4j 2 API provides the same. Support for Commons Logging, slf4j, > Logback, log4j1 and so on. > Just maintained and with a nice api. Oh, and its the fastest logging > library: > http://www.grobmeier.de/log4j-2-performance-close-to-insane-20072013.html > > In my app i have bridged Cayenne logging to log4j2 btw. > It works, but I was wondering why Commons Logging came into play. I would > have understood slf4j (even when I prefer log4j2) > > > >> >> On Tue, Dec 3, 2013 at 8:45 AM, Christian Grobmeier <[email protected]> >> wrote: >>> >>> Commons Logging?? >>> >>> Have you considered Log4j 2? >>> >>> >>> On 3 Dec 2013, at 14:30, Andrus Adamchik wrote: >>> >>>> 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 >>>>> >>> >>> >>> --- >>> http://www.grobmeier.de >>> @grobmeier >>> GPG: 0xA5CC90DB > > > > --- > http://www.grobmeier.de > @grobmeier > GPG: 0xA5CC90DB
