[jboss-jira] [JBoss JIRA] Moved: (JBMX-2) XMBean error checking

[Adrian Brock (JIRA)]

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

Adrian Brock moved JBAS-1700 to JBMX-2:
---------------------------------------

              Project: JBossMX  (was: JBoss Application Server)
                  Key: JBMX-2  (was: JBAS-1700)
          Component/s: xmbean
                           (was: JMX)
    Affects Version/s:     (was: JBossAS-4.0.1 Final)
                           (was: JBossAS-3.2.7 Final)
                           (was:  JBossAS-4.0.2RC1)
                           (was: JBossAS-4.0.1 SP1)
             Security:     (was: Public)


> XMBean error checking
> ---------------------
>
>                 Key: JBMX-2
>                 URL: https://jira.jboss.org/jira/browse/JBMX-2
>             Project: JBossMX
>          Issue Type: Task
>          Components: xmbean
>            Reporter: Adrian Brock
>
> The XMBean error checking needs to be improved such that it can spot errors
> in the signatures rather than assuming the invocation is a "dynamic" request
> based on the descriptors.
> There is even a warning about it in the code,
> AbstractMBeanInvoker.initDispatchers:
> // What is this late binding attempt and should there be a warning?
> dispatcher = new ReflectedDispatcher(dynamicResource);
> Additionally, with the changes in Java5 the return type is no longer
> as significant when resolving methods.
> We need to update this such that it allows "polymorphism" on the return type
> and even allows the returned object to be "eaten" if the descriptor says
> it wants to return "void".

-- 
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