• 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

 
Ranch Hand
Posts: 130
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi all,
my question is about stateful session bean,how does the container remember the state of the conversation, I mean to rememeber the client is there anything in the stubs and skeletons that helps remember the bean instance on the server side? or is there something else?, what happens if I close the Browser or system shut down on the client side and restart again, can I still remember the conversation ? please explain.

thanks
Pradeep
--------------------

SCJP1.4,SCBCD
"Failure is not when you fall down; its only when you fail to get up again."
 
Ranch Hand
Posts: 704
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Praadep,

You might have a point here. Speaking from my experience with WebLogic, I don’t remember the documentation saying exactly how this is achieved. It provides detailed information about clustering any type of enterprise beans only. You might check the documentation for versions before 6, when the clustering was not introduced. If you are interested to get more information about clustering you can check this thread: https://coderanch.com/t/315844/EJB-JEE/java/Session
Without reading any specifications I bet that this is achieved in a very straightforward way: the SFSB stub appends one more attribute to every method. Kind of a serializable cookie that gets passed forward and back from the client to the server, over RMI or T3 protocol. This is my two cents bet and I can’t think of anything else that makes more sense.
Regards.
reply
    Bookmark Topic Watch Topic
  • New Topic