• 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

Confirmation Required

 
Ranch Hand
Posts: 643
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Entity beans survive container crash.
Session beans and MDB does not survive container crash.
MDB are stateless.
 
Ranch Hand
Posts: 218
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Entity beans survive container crash.
Session beans and MDB does not survive container crash.
MDB are stateless.



Entity beans are the in memory representation of some row of a table in DB.
Even if the server crashes the bean instance dies but the db still contains
the data, It can be reloaded from db when the server restarts.

Session beans especially Stateful beans contain the state of the client, if the server crashes the bean dies and the state it held is lost.

Message driven beans do not have any clients and are invoked by the server
on a message. Just a single message onMessage is invoked. It cannot hold any state as the server selects bean's instance at random and as there is no client there is no point in holding a particular state.
 
I've never won anything before. Not even a tiny ad:
a bit of art, as a gift, that will fit in a stocking
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic