This week's book giveaways are in the Refactoring and Agile forums. We're giving away four copies each of Re-engineering Legacy Software and Docker in Action and have the authors on-line! See this thread and this one for details.
In the WebSphere V3.5 Handbook, chapter 11, Enterprise Java Services, pages 444 and 455, sample servlet doGet methods are shown that retain a Stateful Session Bean object and handle reference, respectively, in the HttpSession object in order to re-invoke a Stateful Session Bean. Since the example Session Bean is used only to maintain a counter, may I assume this is simply a contrived example that merely shows how one would maintain a reference to and re-invoke a Stateful Session Bean? If not, it sure seems to me that it would be easier to maintain the counter itself in the HttpSession object. If so, am I correct in assuming that a more real-world example would be, for example, to use a Stateful Session Bean to manage one or more Entity Beans?