• 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

Help....

 
Greenhorn
Posts: 27
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Gurus

Good Morning and please give the answers to my below questions.

i) Which type of bean will survive a container / server crash? why?

ii) When a "stateful session bean" "times out", after being in the "passivated" state, will the container invoke any "call back"(esp. ejbRemove()) method?

Thanks
Vijay.
 
Greenhorn
Posts: 13
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hey,
Hope I can help!

i- Entity Beans will survive a container crash. After all they're persisted in a database. And the data will still be there, unless you execute a DELETE against it

ii- No. For the container to call any callback method, it would have to first activate the instance. And there is no sense in activating a instance just to tell it's dead. You better have your clean-up code in both ejbRemove() and ejbPassivate()

Please all, correct me if I'm wrong!

Cheers!
 
Ranch Hand
Posts: 182
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator


You are just right buddy...
reply
    Bookmark Topic Watch Topic
  • New Topic