Hi Kamal
Decision regarding what to choose depends upon your business
logic.
If you require to Maintain the client conversation, i.e information
regarding the client across multiple method call, then use stateful session
bean. There is some overhead associated with stateful session bean, as state
need to be saved.
If no session is maintained, it is better to use stateless session bean as
they are more scaleable.
If you are using different database, it is better to use BMP entity bean.
I hope this answer your question
regds
Anil
-----Original Message-----
From: Kamal Mishra [mailto:[EMAIL PROTECTED]]
Sent: Saturday, December 30, 2000 1:45 PM
To: [EMAIL PROTECTED]
Subject: Stateful V/s Stateless Session Beans
Hi EJBGurus,
Could anybody tell me how to select for Staeless or Stateful Session Beans
as far as Design aspects are concerned.
Secondly, I have a complex system with ouple of databases to handle. Now I
want to handle these Databases all at one go i.e. from One single site. I
mean the design should be as such. Now in this context How to go and decide
for which type of beans. Stateful or Stateless and if so then WHY ?
Thanks in advance
Kamal
______________________________________________________
123India.com - India's Premier Portal
Get your Free Email Account at http://www.123india.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".
===========================================================================
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".
