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

Marco Zapletal reopened CAMEL-4468:
-----------------------------------

    Estimated Complexity: Novice

I attach a second patch, since in the former one the MBean interfaces do not 
inherit from each other.
This results for the example in the following problem: When proxying a 
ManagedRoute using a ManagedRouteMBean, attributes which ManagedRoute inherits 
from ManagedPerformanceCounter cannot be accessed. The attached patch solves 
that by letting the corresponding MBean interfaces inherit according to the 
inheritance relationships of the ManagedResources.
                
> Providing Interfaces for MBeans to be able to proxy them
> --------------------------------------------------------
>
>                 Key: CAMEL-4468
>                 URL: https://issues.apache.org/jira/browse/CAMEL-4468
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core, jmx
>    Affects Versions: 2.8.1
>            Reporter: Marco Zapletal
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 2.9.0
>
>         Attachments: CAMEL-4468.diff.txt
>
>
> This issue proposes to provide interfaces for the Camel JMX MBeans, which 
> allows to (easily) proxy them on the client side (c.f. 
> http://camel.465427.n5.nabble.com/Providing-Interfaces-for-MBeans-to-be-able-to-proxy-them-td4813271.html#a4813298)
>  
> I would provide the patch for this but before, I ask the core developers for 
> code conventions in terms of the interfaces: In which package should the 
> interfaces be put and how should they be named?
> Should they be put to the MBeans classes in org.apache.camel.management? But 
> how to name them then, since for example IManagedRoute would break current 
> camel naming conventions and identifiers such as ManagedRoute are already 
> taken by the class implementations.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to