Posted in: EJB Interview Questions with Answers
Stateless Session Bean
|
Stateful Session Bean
|
|
Stateless session bean these are single request
business process is one that does not require state to be maintained
across method invocation. Stateless session bean cannot hold the
state.
|
Statefull session bean is a bean that is designed to service business process that span multiple methods request/transaction, S.S.B can retain their state on the behalf of individual client.
|
|
There should be one and only one create method that to without any argument in the home interface.
|
There can be one or more create methods with or without arguments in the Home Interface.
|
|
Stateless session bean instance can be pooled. Therefore “n” number of beans can cater to n+1 number of clients.
|
Statefull session bean do not have pooling concept. Stateful bean will be given individual copy for every user.
|
|
Stateless bean will not be destroyed after client has gone.
|
Stateful bean will be destroyed once the client has gone (or after session time out)
|
|
If the business last only for a single method call, S.S.B are suitable
|
If the business process spans multiple invocations there by requiring a conversational then S.S.B will be ideal choice.
|
|
Stateless session bean cannot have instance variable
|
Stateful session bean will have instance variable and state is maintained in these instance variables
|
|
EjbRemove() method does not destroy the bean , it remains in the pooled state.
|
Stateful bean can be destroyed by calling the ejbRemove() method
|