This week's book giveaway is in the Testing forum. We're giving away four copies of Data Structures the Fun Way: An Amusing Adventure with Coffee-Filled Examples and have Jeremy Kubica on-line! See this thread for details.
Reference: EJB 2.0 Final Release Page: 80/81 ejbRemove() and afterComplete() methods do not operate under a transaction context. on Page 81: Invoking the getCallerPrincipal and isCallerInRole methods is disallowed in session bean methods for which the container does not have a client security context both ejbRemove() and afterComplete() methods can access getCallerPrincipal and isCallerInRole which means that both are in Client Security COntext (is it not?). If afterComplete() is in CLient Security Context it should be able to access resource managers and enterprise beans but the spec says that (on page 80) afterComplete() can't access resource managers and enterprise beans. This is ambiguous to me, could someone explain this? Thanks, Santosh R