Entity Bean - ejbPassivate()

[Santosh Ramachandrula]

Reference: EJB Spec 2.0 Final Release
Page: 169
Container can choose to passivate an entity bean instance with in a transaction


Reference: Head First EJB
Page: 311
Under EntityBean interface
ejbPassivate() called when the bean is about to return to the pool, following a transaction
Are'nt these two sentences contradictory? If they are not can someone explain what do they exactly mean?
[ April 15, 2004: Message edited by: Santosh Ram ]
[ April 15, 2004: Message edited by: Santosh Ram ]

[David Harrigan]

Hi,
I think you are getting slightly confused.
For a stateful *session* bean, you are correct - it will not be passivated whilst in a tx.
For an Entity bean, it may be passivated by the container whilst that Entity bean is participating within a tx.
That is what the spec is alluding to.
-=david=-

[Santosh Ramachandrula]

Hi David,
Thanks for the reponse. I understood what you said. In my question the two statements from two different books and are referening to EntityBean...so I feel that they are contradictory??


Reference: EJB Spec 2.0 Final Release
Page: 169
Container can choose to passivate an entity bean instance with in a transaction
Reference: Head First EJB by Kathy, Bates
Page: 311
Under EntityBean interface
ejbPassivate() called when the bean is about to return to the pool, following a transaction
[ April 16, 2004: Message edited by: Santosh Ram ]

[Sany Bel]

Hi Santosh,
I had the same doubt when I was reading the spec. But then I thought about it and this is what I concluded:
The spec says
Container can choose to passivate an entity bean instance with in a transaction
and it also mentions that

To passivate
an instance, the container first invokes the ejbStore method to allow the instance to prepare
itself for the synchronization of the database state with the instance�s state, and then the container
invokes the ejbPassivate method to return the instance to the pooled state. on page 169 and on page 172 it mentions that ejbPassivate() runs in an unspecified transaction context.
So, I think contains can choose to passivate the bean does not mean that it is calling ejbPassivate() there, it means it is getting ready to passivate and since ejbStore runs in a transaction, it calls ejbStore first and I believe the transaction ends there and then it calls ejbPassivate() in an unspecified transaction context.
I hope this helps and that I haven't confused you even more.

[Santosh Ramachandrula]

Sany Thanks!! You made it clear to me, it was a good explanation.
Santosh

[Ko Ko Naing]

Originally posted by Santosh Ram:
Sany Thanks!! You made it clear to me, it was a good explanation.
Santosh

Yeah, Sany's explanation is great!!!