You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2011/07/05 14:44:16 UTC

[jira] [Updated] (ARIES-702) [Whiteboard] Use introspection to find the MBean interface

     [ https://issues.apache.org/jira/browse/ARIES-702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Felix Meschberger updated ARIES-702:
------------------------------------

    Attachment: ARIES-702.patch

Proposed patch using a new service filter (jmx.objectname=*) to just select the candidate MBeans using the object name (may be empty to require MBeanRegistration interface to be implemented). Uses reflection to find the actual MBean interface defining the MBean and optional wrapping the MBean service with StandardMBean if required.

Note: this patch includes the ARIES-701 patch since it essentially extends that functionality

> [Whiteboard] Use introspection to find the MBean interface
> ----------------------------------------------------------
>
>                 Key: ARIES-702
>                 URL: https://issues.apache.org/jira/browse/ARIES-702
>             Project: Aries
>          Issue Type: Improvement
>          Components: JMX
>    Affects Versions: 0.3
>            Reporter: Felix Meschberger
>         Attachments: ARIES-702.patch
>
>
> The JMX Spec states that standard MBeans must implement an interface whose name is derived from the implementation class by appending the "MBean" suffix and the interface must be located in the same package as the implementation class.
> This is problematic in multiple ways.
> I suggest we change this as follows:
>   * If the service object implements the DynamicMBean interface (or an extension thereof), use the object as is as the MBean
>   * Find the MBean interface by walking up the class and interface hierarchy

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira