[CAMEL-6660] JMX - Using custom @ManagedResource and extending default components can cause some attributes to be unavailable

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.16.0
• Component/s: camel-core, jmx
• Estimated Complexity: Moderate
• Assignee: Claus Ibsen
• Reporter: Claus Ibsen
• Created: 22/Aug/13 13:24
• Updated: 11/Aug/15 13:23
• Resolved: 11/Aug/15 13:23

Description

Related to CAMEL-6586

Its when you use a custom @ManagedResource such as in a custom component, then some of the out of the box attributes such as camelId, state, etc may be shown as Unavailable in JMX consoles.

Its the MBean assembler and JMX in general that needs to find some way of being able to mixin the custom attributes/operations with the out of the box ones. So you dont have to copy the out of the box attributes to your custom classes.

Issue Links

• is depended upon by: CAMEL-9074 Camel components - Add @ResourceEndpoint to endpoints to expose custom information
• is duplicated by: CAMEL-8147 Using @ManagedResource on an Endpoint removes all the default JMX properties
• relates to: CAMEL-6586 JMX - browsable endpoints such as seda has some attributes listed as unavaiable