I'm trying to understand the rules for when it is permissible for a bean to access the methods of another bean. I thought that this could be done while the bean was in a transaction. If this is the case then why can it be done in ejbCreate() for a session bean?
My understanding is that you can specify a transaction attribute for the ejbCreate() methods of entity beans but not session beans. Does the container automatically assign a transaction attribute of "Required" to certain session bean callbacks? Why is it permissible to access another EJB from ejbCreate(), ejbActivate(), ejbRemove(), and ejbPassivate() but not afterCompletion()?
Robert
My understanding is that you can specify a transaction attribute for the ejbCreate() methods of entity beans but not session beans. Does the container automatically assign a transaction attribute of "Required" to certain session bean callbacks? Why is it permissible to access another EJB from ejbCreate(), ejbActivate(), ejbRemove(), and ejbPassivate() but not afterCompletion()?
Robert