[jboss-jira] [JBoss JIRA] Commented: (JBAOP-546) MethodHashing.methodHash(Method) Does Not Account for Declaring Class or Throws Clause

[Andrew Lee Rubinger (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBAOP-546?page=comments#action_12404840 ] 
            
Andrew Lee Rubinger commented on JBAOP-546:
-------------------------------------------

Hmm..we may have to use a different mechanism then.

Here's a use case:

public interface MyBusinessRemote{
  void remove();
}

public interface MyRemote extends EJBObject{
}

@Stateful
@Remote({MyRemote.class, MyBusinessRemote.class})
@RemoteHome(MyRemoteHome.class)
public class MyBean implements MyBusinessRemote {
  
  void remove(){
    // This won't get called because MethodHashing sees
    // this method as equal to EJBObject.remove()
    // and instead the SFSB will be removed.
  }
}


> MethodHashing.methodHash(Method) Does Not Account for Declaring Class or Throws Clause
> --------------------------------------------------------------------------------------
>
>                 Key: JBAOP-546
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-546
>             Project: JBoss AOP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Andrew Lee Rubinger
>         Assigned To: Kabir Khan
>         Attachments: JBAOP-546.patch
>
>
> Kabir:
> EJB3 is using method hashing to uniquely key Invocations to MethodInfo; in the case that two interfaces define the same signature, but with different declaring classes or throws clauses, there is overlap and overwrite.
> S,
> ALR

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira