-
Bug
-
Resolution: Done
-
Critical
-
None
-
None
Methods are identified by AOP based on their hash code.
Regardless of interface 'void remove()' will always have the same hash.
Thus the method is interpreted by the container as being an EJBObject.remove() or EJBLocalObject.remove and goes through the EJB 2.1 view logic. (Regardless of whether it is actually annotated with @Remove!)
- is blocked by
-
EJBTHREE-1621 Virtual Methods are registered from EJB Implementation Class, Declaring Interfaces Ignored
- Open
-
EJBTHREE-1269 Add Serializable invokedMethod view to Invocation Metadata
- Resolved
- is related to
-
EJBTHREE-1353 EJBContainer.isCallable is doing string comparison using the '==' operator
- Closed
-
EJBTHREE-1253 Session Implementations of javax.ejb.Handle cannot cast to EJBObject from JNDI
- Resolved
- relates to
-
EJBTHREE-1060 getInvokedBusinessInterface doesn't return correct interface
- Resolved
-
EJBTHREE-786 String remove() method on SFSB
- Closed
-
EJBTHREE-1154 2.1 Home create() implementation returns wrong type
- Closed