[jboss-dev-forums] [Design of EJB 3.0] - Normal SFSB Business Methods named "remove"

This one has been unaddressed for awhile now. It's the failing case associated with: https://jira.jboss.org/jira/browse/EJBTHREE-1222 Target methods are resolved based upon a hash, and the hashing function does not take the declaring class into account, thus business interfaces and EJBObject resolve their "remove" methods identically: https://jira.jboss.org/jira/browse/JBAOP-546 This cannot be fixed (to take declaring class into account). Further, we can't swap out our use of the AOP MethodHashing for our own because we only directly hash and populate the method tables for "virtual" methods; all others are done by AOP ClassAdvisor, and we don't have the hooks (presently) to redefine the hash function to be applied. So maybe our best hope is to extract out the hashing logic into a method we can override in ExtendedManagedObjectAdvisor; then ClassAdvisor calls will use our impl. S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4195767#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...