Hi dhanu, We have a naming policy here at JavaRanch where all publicly displayed names take the form, "Firstname surname". Could you please change yours to bring it into line? Thanks in advance and we hope that you enjoy your stay at the ranch! Cheers Simon
It's pretty clear from reading the spec (and true in pretty much every implementation) that the default is that the state of a stateful session bean is simply held in an in-memory object; a unique instance of the bean implementation class. That is why we have passivation for stateful session beans -- if the number of bean instances exceeds a preset limit in the container (indicating that too much of the heap is being taken up) then some of the excess beans of that type will be passivated (saved to a file on the disk in serialized form). Kyle
Originally posted by dhanu: How container is maintaining state for stateful session bean behind the scene? I need a clear idea. Can anybody clarify it?
Hi, In Stateful Session Bean after every method calls the information will be stored in the secondary storage medium. And when stateful session bean calls a method it will check the client information details, and retrieve the corresponding data from the secondary storage medium. Regards, M.S.Raman
Hi Sudha, I dunno if you got what you were looking for or not but here is what i will add: Stateful session beans are just like the instances of a Class which is non static while as Stateless session beans are just like abstract classes or static classes if u like (once a C++ lover, always a C++ lover). So that way the state can be maintained across invocations to stateful session beans but not across stateless session beans. Rest everything is said up there. Thnx :-) Sahil