Lavanya

• Apr 17th, 2005

 

a) Stateful beans are also Persistent session beans. They are designed to service business processes that span multiple method requests or transactions. 
 
Stateless beans are designed to service business process that last only for a single method call or request. 
 
b) Stateful session beans remembers the previous requests and reponses. 
Stateless session beans do not remember the previous request and responses. 
 
c)Stateful session beans does not have pooling concept. 
Stattless session bean instances are pooled. 
 
d) Stateful S.Beans can retain their state on behave of an individual client. 
Stateless S.Beans donot maintain states. 
 
e) Stateful S.Beans can be passivated and reuses them for many clients. 
Stateless S.Beans, client specific data has to be pushed to the bean for each method invocation which result in increase of network traffic. 

Mohan

• May 20th, 2005

 

Stateful session beans have the passivated and Active state which the Stateless bean does not have.

Deepak

• Aug 27th, 2005

 

There is another important point which all of you guys have failed to mention. The important point is that Stateless Session beans are scaleable and can therefore be replaced by an enhanced model whereas Stateful Session beans are not scaleable.

stephen

• Oct 3rd, 2005

 

     state full session bean will maintain the state of the client with server.with activate&passivate methods.

      state less session bean will not maintain the state.

   

Jeevan Sunkersett

• Jul 16th, 2007

 

Stateful Session Bean (SFSB) do not have the concept of pooling

srikanthm2

 Profile Answers by srikanthm2 Questions by srikanthm2

• Jan 28th, 2008

 

Stateful session beans follow the instance passivation technique
Stateless session beans follow the instance pooling technique.

ejbActivate() and ejbPassivate() methods are not called in Stateless session beans

I