Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
Mime-Version: 1.0 (Apple Message framework v752.2)
In-Reply-To: <851F29E7-DC8A-452F-8634-6CF5B15BCC61@objectstyle.org>
References: <93ACF16B-B5BF-4D29-9C70-48C9C7E6C2B5@yahoo.com>
 <851F29E7-DC8A-452F-8634-6CF5B15BCC61@objectstyle.org>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <EE994D03-8A6D-4AD6-9637-B006767F2C73@iq80.com>
Content-Transfer-Encoding: 7bit
From: Dain Sundstrom <dain@iq80.com>
Subject: Re: Some jpa questions
Date: Thu, 24 Aug 2006 16:10:14 -0700
To: dev@geronimo.apache.org

On Aug 24, 2006, at 1:50 PM, Andrus Adamchik wrote:

>> 2. What's supposed to happen when you try to use a CM tx scoped EM  
>> outside a JTA tx?  Section 5.6.1 seems to imply we aren't supposed  
>> to just throw an exception, but section 5.9.1 seems to imply there  
>> is no provider EM in back of the CM EM to do any work without a  
>> JTA tx.  Are we supposed to create and close a provider EM for  
>> each call outside a tx?
>
> Good question... I have no idea.

 From what I understand, yes.

>> - How heavyweight are EntityManagers?
>
> I guess this could be implementation specific, but they are  
> lightweight in Cayenne, and I assume they are lightweight in other  
> providers as well.
>
>> Is it more efficient to create a new one or pool them?
>
> While the spec provides some leeway (see below), container with  
> pluggable provider has no way of knowing the best strategy. My vote  
> is to avoid pooling EntityManagers by default.

+1 If it later becomes an issue we can introduce pooling.

My guess is that most providers are pooling under the covers since  
the largest user group will be unmanaged servlets which don't do app  
level pooling.

-dain