Andreas Vogel wrote:
>
> Entity beans are specifically targeted towards transactions. Caching is a value
> add of CMP implementation BMP prevents you from caching.
>
Why would that be? I thought a container could keep entity bean data in
memory no matter if CMP or BMP? My understanding was that say client 1
requests an entity bean instance with PK x which is not in main memory.
It is retrieved from the DBMS (CMP or BMP) and instantiated in main
memory. Then client 2 also requests the entity with PK x, which then may
still be in main memory. Where is the difference between CMP or BMP
here? It may very well be that I'm misunderstanding the spec as I am not
an expert. Could you please enlighten my on that point as it seems to be
a very important factor in designing an EJB application using entity
beans with BMP with acceptable performance.
Thanks,
Robert
--
(-) Robert Kr�ger
(-) SIGNAL 7 Gesellschaft f�r Informationstechnologie mbH
(-) Br�der-Knau�-Str. 79 - 64285 Darmstadt,
(-) Tel: 06151 665401, Fax: 06151 665373
(-) [EMAIL PROTECTED], www.signal7.de
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
