eted
by Orion itself...
Geoff
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]] On Behalf Of
> Geoff Soutter
> Sent: Friday, 11 January, 2002 9:09 AM
> To: Orion-Interest
> Subject: RE: Simple question re caching/pooling of BMP Entity Bean
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]] On Behalf Of
> Geoff Soutter
> Sent: Friday, 11 January, 2002 9:09 AM
> To: Orion-Interest
> Subject: RE: Simple question re caching/pooling of BMP Entity Beans
>
>
> Hi Sergey,
>
gt;
> Geoff
>
>
>> -Original Message-
>> From: [EMAIL PROTECTED]
>> [mailto:[EMAIL PROTECTED]] On Behalf Of
>> Sergey G. Aslanov
>> Sent: Thursday, 10 January, 2002 6:29 PM
>> To: Orion-Interest
>> Subject: Re: Simple question re cachi
iday, January 11, 2002 8:08 AM
Subject: RE: Simple question re caching/pooling of BMP Entity Beans
> Hi Sergey,
>
> Thanks for the reply. I didn't explain it very clearly did I? What I
> meant was:
>
> "However, it appears that it goes to the database (i.e. ca
> To: Orion-Interest
> Subject: Re: Simple question re caching/pooling of BMP Entity Beans
>
>
> Hi Geoff
>
> Loading of beans have these stages:
> 1. calling ejbFindBy... to get the primKeys of the entities;
> 2. checking if entities with such keys are already poo
My opinion would add;
if not pooled OR not exclusive owner of data then ejbLoad
exclusive owner is an orion-ejb-jar.xml propert. The default is,
exclusively owns the data.
curt
Sergey G. Aslanov wrote:
>Hi Geoff
>
>Loading of beans have these stages:
>1. calling ejbFindBy... to get the pr
Hi Geoff
Loading of beans have these stages:
1. calling ejbFindBy... to get the primKeys of the entities;
2. checking if entities with such keys are already pooled;
3. for every key checking: if not pooled - call ejbLoad, else - get instance
from pool;
As you see, ejbFindBy... are called always