I would like to know what approaches people are taking to design entity
beans so that they behave in a read only manner and are sharable across
users. I am really interested in a portable design not BEAs read only
beans.
For example, if you have a catalog of products, ideally I would like to
populate a bean with a product once and all subsequent users of the bean
would access that instance and not have to repopulate or go to the database
each time. In my use so far, I notice that every call to the beans methods
results in the ejbload and ejbstore methods being called, making the
operation very expensive in terms of database calls.
any thoughts?
Thanks
Tom.
________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com
===========================================================================
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".
