• 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 all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Paul Clapham
  • Jeanne Boyarsky
  • Junilu Lacar
  • Henry Wong
  • Ron McLeod
  • Devaka Cooray
  • Tim Cooke
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Frits Walraven
  • Tim Holloway
  • Carey Brown
  • Piet Souris
  • salvin francis
  • fred rosenberger

Kathy & Bert Is this a Gotcha?

Ranch Hand
Posts: 187
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
There seems to be a imperfect explanation / illustration on page 211 of K&B HFEJB.

In section "Container decides to kill the bean but does not call ejbRemove()." It shows the container sending to the gc the passivated bean for garbage collection.

When a bean is passivated it means that the bean is already either sent to gc (or maybe recycled [not per spec]) to reduce the number of bean objects on the heap.

In section "Container decides to kill the bean but does not call ejbRemove()." The book should show the container deleting the file conatining the bytes of the serialized bean from the file persistence system( or whatever means was used for serialization).
He was giving me directions and I was powerless to resist. I cannot resist this tiny ad:
Devious Experiments for a Truly Passive Greenhouse!
    Bookmark Topic Watch Topic
  • New Topic