You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2010/12/07 10:50:09 UTC

[jira] Resolved: (CAMEL-3399) Tidying up strategy for managing resources in JMX

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

Claus Ibsen resolved CAMEL-3399.
--------------------------------

    Resolution: Fixed

trunk: 1042949.

> Tidying up strategy for managing resources in JMX
> -------------------------------------------------
>
>                 Key: CAMEL-3399
>                 URL: https://issues.apache.org/jira/browse/CAMEL-3399
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core, jmx
>    Affects Versions: 2.5.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 2.6.0
>
>
> The management strategy should be
> 1) use ManagementAware if implemented on bean
> 2) use @ManagedResource if provided on bean
> 3) otherwise use default
> Consider using fallback from 1->2 which is the current behavior. If we change this we will break backwards compatibility.
> But in essence we should had Camel fail if (1) cannot be registered, and not just fallback to use (2) as it does today.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.