Help coderanch get a
new server
by contributing to the fundraiser
  • 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 ...
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
  • Mikalai Zaikin

Stateless vs Stateful Session Beans

Posts: 14
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I am working with both stateless and stateful sesssion beans within Visual age for Java. I was wondering if anyone could give me a general overview of the proper way to invoke/use these beans. I was told it was best to cache the EJBHome object and continually call the create() method to obtain the remote object when working with stateless beans.
Meanwhile, if maintaining state for a single user with stateful beans it is best to cache a remote object unique to that user. Does the developer rely on a session to cache this object or is an id sent to the bean each time? Is any of this information accurate....if not what is the best practice?
Thanks a lot,
He loves you so much! And I'm baking the cake! I'm going to put this tiny ad in the cake:
We need your help - Coderanch server fundraiser
    Bookmark Topic Watch Topic
  • New Topic