Mailing-List: contact user-help@cayenne.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cayenne.apache.org
Received-SPF: pass (athena.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=dk20050327; d=earthlink.net;
  b=o1Jpl/QfOnLH+vNsR+tXXOLQ9iQKOmJwEtEuf1Cb1CPrJJt32b4jE0yRafiYdf7k;
  h=Received:Message-Id:From:To:In-Reply-To:Content-Type:Content-Transfer-Encoding:Mime-Version:Subject:Date:References:X-Mailer:X-ELNK-Trace:X-Originating-IP;
Message-Id: <8C924D64-98E1-4751-A511-7A5F98249A50@earthlink.net>
From: Joe Baldwin <jfbaldwin@earthlink.net>
To: user@cayenne.apache.org
In-Reply-To: <B733C97D-CFEB-43B6-B98A-B2328BB6DAE7@objectstyle.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Subject: Re: Cayenne logging
Date: Thu, 11 Jun 2009 12:01:23 -0400
References: <cf4fbd7e0906091414y5e6af46dp58ed1d2fcfbb1030@mail.gmail.com>
 	<EF6BD257-4A8E-4C69-9F1D-0C405F43ECAE@objectstyle.org>
 <cf4fbd7e0906100752p5c18b9e1w21896de432506bc@mail.gmail.com>
 	<6E39D30A-4C08-4D36-B91D-233F834B884B@objectstyle.org>
 <cf4fbd7e0906100851r359efb20i7467ddd53fcf81d5@mail.gmail.com>
 <4A311112.5040905@gmail.com> <4A311301.7040805@maniatis.org>
 <5CF274C8-75BE-4C6C-BE01-AEAD1D041EEC@earthlink.net>
 <E92AC5F8-DCCB-4F81-8C3C-0E1764E93DE7@objectstyle.org>
 <E717AB9A-759F-4E3A-83CE-5D3AC66051DA@earthlink.net>
 <B733C97D-CFEB-43B6-B98A-B2328BB6DAE7@objectstyle.org>

Andrus,

Thanks for the apache logging link.

Concerning:

> In short, when your application starts, and before Cayenne is  
> loaded, you have to manually bootstrap log4j using  
> PropertyConfigurator class, specifying the config file:
>
>  PropertyConfigurator.configure(myFile);
>
> This way you can't possibly misplace the config file (you'll get an  
> exception), and all your logging configuration will be accounted for.


I remember reading this in your docs.  However, since the scenario is  
a Tomcat webapp, I am not exactly sure where it is in the code that  
the app "starts".  I think that this was a topic in your discussion  
(that I read, possibly for an older version), and it suggested that  
the cayenne-log.properties should be placed in a hidden directory  
".cayenne" in the search path (which, I assume for a WebApp is either  
WEB-INF/lib or WEB-INF/config/cayenne-files - if you use the web.xml  
filter).   <= could not get either of these to work btw.

I am in total hack-mode and am looking for the "ON/OFF" switch. :)

Joe


On Jun 11, 2009, at 11:40 AM, Andrus Adamchik wrote:

> I see, sorry for the confusion.
>
> As an aside Log4J *project* seems to be either dead or on life  
> support, abandoned by its authors, who moved to write the new  
> logging frameworks, which may or may not work with commons-logging.  
> Still the latest stable version of Log4J works great. Just figured  
> I'd mention..
>
> This Log4J doc may get you started:
>
> http://logging.apache.org/log4j/1.2/manual.html
>
> In short, when your application starts, and before Cayenne is  
> loaded, you have to manually bootstrap log4j using  
> PropertyConfigurator class, specifying the config file:
>
>  PropertyConfigurator.configure(myFile);
>
> This way you can't possibly misplace the config file (you'll get an  
> exception), and all your logging configuration will be accounted for.
>
> Andrus
>
>
> On Jun 11, 2009, at 5:59 PM, Joe Baldwin wrote:
>> Andrus,
>>
>> I have not used log4j very much and definitely am not an expert at  
>> configuring it.  I have not been able to implement the instructions  
>> found at
>> 	http://cayenne.apache.org/doc/configuring-logging.html
>> so that I can control logging.
>>
>> Quoting from 3.0M6 docs on your website:
>> 	"Commons-logging allows users to choose their own logging  
>> provider, such as Log4J or java.util.logging."
>> This is what I was attempting to convey in my last message (sorry,  
>> I was not trying to comment on 2.0 configuration)
>>
>> Furthermore, when I attempted to implement the example to turn SQL  
>> tracing off:
>> 	log4j.logger.org.apache.cayenne.access.QueryLogger = WARN
>> I  found that there was no change in the output.
>>
>> So I can only assume that I am missing some fundamental part of the  
>> primer.  My last theory is that I have either placed my cayenne- 
>> log.properties file in the wrong location, or I my configuration  
>> parameters are incomplete.
>>
>> Do you have any suggestions.
>>
>> Joe
>>
>>
>>
>>
>> On Jun 11, 2009, at 10:37 AM, Andrus Adamchik wrote:
>>
>>>
>>> On Jun 11, 2009, at 5:32 PM, Joe Baldwin wrote:
>>>
>>>> docs say that you can use either
>>>
>>> This can't be true... If you put org.objectstyle in the logging  
>>> config, it will have zero effect in 2.0 and 3.0.
>>>
>>> Andrus
>>>
>>
>