Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
To: dev@cocoon.apache.org
From: Olivier Billard <obillard@rennes.jouve.fr>
Subject: Re: Use of a connection in an avalon component
Date: Thu, 09 Oct 2003 15:33:21 +0200
Lines: 38
Message-ID: <bm3o33$6em$1@sea.gmane.org>
References: <bm10fv$9rn$1@sea.gmane.org> <3F855E35.9090001@anyware-tech.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.5) Gecko/20030916
In-Reply-To: <3F855E35.9090001@anyware-tech.com>
Sender: news <news@sea.gmane.org>


On 09/10/2003 15:10, Sylvain Wallez wrote:

> Olivier Billard wrote:
> 
>> Hi all !
>>
>> I wonder how to use a DataSourceComponent and its connection in a 
>> custom cocoon avalon component, that is ThreadSafe, to use all 
>> performance and connection pool used in Cocoon.
>>
>> Should I :
>>  - get a connection via datasource.getConnection() and close() it for 
>> each public method call,
>>  - get a connection in the initialize() method from the interface 
>> Initializable, close() it on the dispose() method from Disposable 
>> interface, and only create a Statement for each public method call ?
>>  - implement another avalon interface, like Runnable, to get/relase 
>> the Connection ?
>>
>> I looked for exemples in the databases block, but the helpers are not 
>> Components. 
> 
> 
> 
> If your component is ThreadSafe, a single instance of it will exist in 
> the whole system. JDBC connections being non thread safe, you *must* get 
> and close them at each call. Don't be afraid to call close(): the 
> connection you get is a wrapper managed by the DataSourceComponent which 
> puts back the real request in the pool for later reuse when close() is 
> called on the wrapper.

by later reuse, do you mean datasource.getConnection() ?

-- 
Olivier