camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CAMEL-6660) JMX - Using custom @ManagedResource and extending default components can cause some attributes to be unavailable
Date Sat, 11 Jul 2015 06:48:04 GMT

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

Claus Ibsen updated CAMEL-6660:
-------------------------------
    Estimated Complexity: Moderate  (was: Unknown)

> JMX - Using custom @ManagedResource and extending default components can cause some attributes
to be unavailable
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-6660
>                 URL: https://issues.apache.org/jira/browse/CAMEL-6660
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core, jmx
>            Reporter: Claus Ibsen
>             Fix For: Future
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message