This is the model we're using on the project I'm working on. Where we need to access a block of records, e.g. query results, we use session beans. When the user selects one of those records to work with, then we use an entity bean for that record.
-tb
-----Original Message-----
From: Kenneth D. Litwak [SMTP:[EMAIL PROTECTED]]
Sent: Friday, April 14, 2000 3:53 PM
To: [EMAIL PROTECTED]
Subject: Most compelling reasons/scenarios for Entity beans?
Im not looking to start a debate. I'm in faovr of EJbs. What I need are the
most compelling reasons or application scenarios for using an entity bean. Fro
my perspective, an entity bean is approrpiate if you need to change multiple
pieces of a data in a specific "record", rather than doing a browse-kind of
operation. I wouldn't use entity beans to do an update on all the "records" I
needed to modify, but I owuld use it to change one speciifc row,object, etc.
What do you think? Thanks.
Ken
===========================================================================
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".
***************************************************************************************
WARNING: All e-mail sent to and from this address will be received or
otherwise recorded by the A.G. Edwards corporate e-mail system and is
subject to archival, monitoring or review by, and/or disclosure to,
someone other than the recipient.
***************************************************************************************
