We're at a bit of a loss over when to use entity beans vs building
stateless session beans. Stateless session beans seem to have a
distinct performance advantage over entity beans and it seems like it
would be wiser to use stateless session beans whenever possible to build
a scalable application. The J2EE model (Developing Enterprise
Applications with Java 2 Platform, Enterprise Edition, December 15,
1999) gives the example of the account object in Duke's Pet Store, but
even that one seems a little weak.
Can anyone shed a little more light on the subject beyond what is in the
J2EE doc?
Thanks,
Scot Cunningham
http://www.seidata.com/~scunning
[EMAIL PROTECTED]
===========================================================================
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".
