Details
-
Bug
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
1.0.0-alpha-2
-
None
Description
EJB interceptor checks in its own @AroundInvoke whether the method is a business method but it:
*) only considers local interfaces, but remote and bean-local view methods must be interceptable (whether or not they are 299 bean-types)
*) is unnecessary since the EJB container only calls this @AroundInvoke for business method invocations
Also, the warning for Object.class methods is duplicated in the @AroundInvoke and our EJBBeanProxyHandler. I think we should remove it from the former, since it only applies to contextual reference.