This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
well, stateless beans will surely change their states if after finishing with 1st operation..so for keeping record of that we need to create a timer object in case we need to retrieve or back-check the status...
vice versa, state full session beans will be automatically saving their states for particular session... and, after that session will complete it will loose state of beans as it will not required now...as session has got over..!
Originally posted by Rahul Ba: Why stateful session beans cannot create timer objects but they do in Stateless???