camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (Commented) (JIRA)" <>
Subject [jira] [Commented] (CAMEL-4468) Providing Interfaces for MBeans to be able to proxy them
Date Tue, 06 Dec 2011 07:31:40 GMT


Claus Ibsen commented on CAMEL-4468:

Thanks for the patch. I had to polish it
- fix checkstyle
- add license headers
- remove annotations from the classes
- improved mbean info assembler to detect the annotations from the interfaces
- fix a few missing attributes in the interfaces
- add unit test that uses the client api
- add package.html for the new package
> Providing Interfaces for MBeans to be able to proxy them
> --------------------------------------------------------
>                 Key: CAMEL-4468
>                 URL:
>             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.

> 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 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:!default.jspa
For more information on JIRA, see:


View raw message