I would pick:
> 3. SLSB -> One BMP, implementing my own persistence by joining the
> tables and using the container
> to cache the data.
Advantages:
- don't have to roll your own caching/DAO or complicate by
adding more libraries
- the (Local!) BMP can do some opitimized SQL queries to end up
only with the data that is really needed
- if at some point performance becomes an issue then you can
re-implement the SLSB (Facade) to use something other than a BMP
entity bean
Strange how so often on this list people are quick to jump on
non-EJB solutions, makes we wonder if the app server they are
using is really worthwhile.
-- Sam
__________________________________________________
Do you Yahoo!?
Yahoo! Web Hosting - Let the expert host your site
http://webhosting.yahoo.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".
