I have an update if anyone can provide some insight. I have been debugging
through the stack when I call camelContext.addService(instance), and I see
why my @ManagedResource class is not getting picked up. As a quick
indirectly related side point, this makes me wonder why my
other
Thank you. This helped get me much further in this effort. The thing that
I am having problems with, now, is that when I annotate the class
with @ManagedResource, and then include @ManagedAttribute to methods, it
will not show up as an MBean. If I remove the @ManagedResource annotation
from the
It needs to be added as a service.
in the producer you can do something ala
doStart
ControlService cs = new
context.addService(cs);
And remove the service in doStop
See for example SendProcessor, or do a
git grep "addService("
And look in the code for other examples
On Wed, Jan 3,
An instance is created in the control producer. How should it be created
in order to be managed?
On Wed, Jan 3, 2024, 3:59 AM Claus Ibsen wrote:
> Hi
>
> You should not overwrite start and stop methods. But implement doStart /
> doStop if you need any logic.
>
> And how do you create
Hi
You should not overwrite start and stop methods. But implement doStart /
doStop if you need any logic.
And how do you create DynamicRouterControlService in the first place
On Tue, Jan 2, 2024 at 11:40 PM Steve973 wrote:
> Hi, all. I was talking about this on the users list, but I found
Hi, all. I was talking about this on the users list, but I found out about
the dev list, so I wanted to share this question with fellow camel
devs/contributors.
I am adding JMX reporting and control to my dynamic router eip component
(not the original dynamic router that you can use with the DSL
