[jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1677) Incorrect handling of overloaded methods in ServiceMBeanDelegate

jaikiran pai (JIRA) jira-events at lists.jboss.org
Mon Jan 12 02:34:14 EST 2009


     [ https://jira.jboss.org/jira/browse/EJBTHREE-1677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

jaikiran pai updated EJBTHREE-1677:
-----------------------------------

          Environment: JBossAS-4.2.x, JBossAS-5.0 GA  (was: JBossAS-4.2.x)
    Affects Version/s: 1.0.0-Beta11


Reproducible on trunk too.

> Incorrect handling of overloaded methods in ServiceMBeanDelegate
> ----------------------------------------------------------------
>
>                 Key: EJBTHREE-1677
>                 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1677
>             Project: EJB 3.0
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.0.0-Beta11
>         Environment: JBossAS-4.2.x, JBossAS-5.0 GA
>            Reporter: jaikiran pai
>            Assignee: jaikiran pai
>
> When a @Service is exposed through a @Management interface and the management interface has overloaded methods, then there are chances of invoking an incorrect method. See the forum reference thread for details. 
> The ServiceMBeanDelegate maintains a Map of signature --> Method, but looks it up incorrectly 
> private Method getOperation(String actionName, String[] signature) throws ReflectionException
>    {
>       String opSig = getOperationSignature(actionName, signature);
>       Method operation = operations.get(actionName); // Incorrect lookup : should be looking up using opSig   

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

        



More information about the jboss-jira mailing list