Excuse the question from someone new to EJB --
I am in a group working on an EJB application using
WebLogic, and we would like to implement our
functionality by using only Entity Beans with state
maintained on the client (applets).
Can anyone think of any significant gotcha's with this
approach? Idea is to minimize establishing session
beans if we really don't need them.
Please excuse me if this is an old question.
Thanks,
- Mark
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.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".