camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matteo Mortari (JIRA)" <>
Subject [jira] [Commented] (CAMEL-7018) Using custom beans with @ManagedResource shows unavailable standard attributes
Date Wed, 10 Dec 2014 16:22:13 GMT


Matteo Mortari commented on CAMEL-7018:

Hi, this solves for the use case in description 'custom bean'.
However if I define a +custom Processor+, possibly I annotate with @ManagedResource to expose
my own attr/ops, but shouldn't this case _indeed_ expose also the Camel's default attrs/ops
for a ManagedProcessor?

The problem I believe is this line, modified in the changelog of this bug:
would actually make expose for a custom Processor _only_ my own annotated attr/ops. But being
my custom Processor a ManagedProcessor at runtime, I would have expected it to expose on JMX
both the custom and Camel's default attr/ops.

It seems to me same problem described here:
And same I experienced today.

I would like to know if this is intended, and how to mitigate for a custom processor, please?
I think this could be a sort of unexpected behavior to some users, and from the faq
to me at least is not clear how to mitigate for a custom processor.

> Using custom beans with @ManagedResource shows unavailable standard attributes
> ------------------------------------------------------------------------------
>                 Key: CAMEL-7018
>                 URL:
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core, jmx
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 2.11.3, 2.12.3, 2.13.0
>         Attachments: jmx-custom-bean.png
> If you have a custom bean with @ManagedResource and your own attr/ops then Camel adds
its default attrs/ops which it should not as they are not available.
> See screenshot

This message was sent by Atlassian JIRA

View raw message