• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Stateful Session Bean Invocation

 
Ranch Hand
Posts: 282
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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?
 
Consider Paul's rocket mass heater.
reply
    Bookmark Topic Watch Topic
  • New Topic