Hi,
We have taken the following path to using entity beans with dependant
objects and would like to know from others if the approach is valid and if
there are performance or scalability issues that might arise from the
design.
Thanks in Advance
Tom.
Example:
User is an Entity bean, and it has a 1 to n releations with Address .
Address is a normal java class. Persistence is handled by the Userbean. The
user bean maintians a collection that contains address object. Here is where
the confusion starts:
When ever you call a business method, the ejb container calls ejbLoad().
Originally on the call to ejbLoad() we were reloading the address collection
each time, which I thought was very poor for peformance. I only want address
to be reloaded when either a new user is created (in which the collection is
emptied) or when we have a new user and the finder method is called. What is
the best way to do this?
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
===========================================================================
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".
