sean mullins

The thing to remember about ejbActivate and ejbPassivate is that they have completly different meanings for Session beans versus Entity beans.
HFEJB has a good synopsis on page 308.

So then is it fair to say that afterCompletion() is some kind of special state, with unspecified transaction context and some sort of "partial" client security context (as it can access getCallerPrinciple and isCallerInRole),
but can't access things like resource managers and other enterprise beans that should be accessible in a "normal" client security context?

Originally posted by Vish Kumar:
Perhaps this feature helps the vendor more than the developer.
I wonder if bean developers ever actually subclass CMP entity beans :roll:

One reason might be if you developed a cmp solution and needed to convert to bmp for whatever reason - container didn't do what you needed, etc. So subclassing the cmp would be a relativly clean solution. Having said that, I've never done this myself (yet anyway)