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)
Message-Id: <82D93953-4A3A-477E-8D22-263C8D4DDEC1@objectstyle.org>
From: Andrus Adamchik <andrus@objectstyle.org>
To: user@cayenne.apache.org
In-Reply-To: <4C19DC08.6040905@tsi-solutions.nl>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Subject: Re: cayenne log4j configuration
Date: Thu, 17 Jun 2010 11:30:29 +0300
References: <4C19DC08.6040905@tsi-solutions.nl>

 From what I can tell, there's probably no way around other than  
either configuring the appenders or moving to 3.0.

Andrus

On Jun 17, 2010, at 11:25 AM, Hans Pikkemaat wrote:

> Hi,
>
> I'm using cayenne 2.0.4. and have my own log4j.xml configuration.
> My configuration does not have any appenders for the root logger.
>
> Looking at the isLoggingConfigured method in the Configuration class  
> I see
> that cayenne assumes that log4j is not setup when the root logger  
> does not
> have any appenders.
>
> So what is happening now is that after processing my log4j  
> configuration file
> cayenne is also processing its configuration file.
>
> See log4j debug logs:
>
> log4j: Using URL [file:/data/projects/common/paymentservice/model/ 
> trunk/target/test-classes/log4j.xml] for automatic log4j  
> configuration.
> .
> .
> log4j: Reading configuration from URL file:/data/projects/common/ 
> paymentservice/model/trunk/target/test-classes/.cayenne/cayenne- 
> log.properties
>
> Is there a way around this except from moving to cayenne 3?
>
> tx
>
> Hans
>