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/20 15:58:01 UTC

[jira] Created: (CAMEL-3448) Exception policies stores in ErrorHandlerSupport should include route id in key

Exception policies stores in ErrorHandlerSupport should include route id in key
-------------------------------------------------------------------------------

                 Key: CAMEL-3448
                 URL: https://issues.apache.org/jira/browse/CAMEL-3448
             Project: Camel
          Issue Type: Bug
          Components: camel-core
    Affects Versions: 2.5.0, 2.4.0, 2.3.0, 2.2.0, 2.1.0, 2.0.0
            Reporter: Claus Ibsen
            Assignee: Claus Ibsen
             Fix For: 2.6.0


If you have a clash with route scoped onException and have the exact same class, then the key in the map isn't catering for this. And thus a 2nd route could override the 1st route onException definition.

For example:

from X route A
  onException IOException

from Y route B
  onException IOException

The map should contain 2 entries, but unfortunately it only contain 1. This only happens when its an exact type match.


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

[jira] Updated: (CAMEL-3448) Route scoped onException may pick onException from another route if they are the same class type

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CAMEL-3448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen updated CAMEL-3448:
-------------------------------

    Summary: Route scoped onException may pick onException from another route if they are the same class type  (was: Exception policies stores in ErrorHandlerSupport should include route id in key)

> Route scoped onException may pick onException from another route if they are the same class type
> ------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-3448
>                 URL: https://issues.apache.org/jira/browse/CAMEL-3448
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 2.0.0, 2.1.0, 2.2.0, 2.3.0, 2.4.0, 2.5.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Critical
>             Fix For: 2.6.0
>
>
> If you have a clash with route scoped onException and have the exact same class, then the key in the map isn't catering for this. And thus a 2nd route could override the 1st route onException definition.
> For example:
> from X route A
>   onException IOException
> from Y route B
>   onException IOException
> The map should contain 2 entries, but unfortunately it only contain 1. This only happens when its an exact type match.

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

[jira] Updated: (CAMEL-3448) Exception policies stores in ErrorHandlerSupport should include route id in key

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CAMEL-3448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen updated CAMEL-3448:
-------------------------------

    Priority: Critical  (was: Major)

> Exception policies stores in ErrorHandlerSupport should include route id in key
> -------------------------------------------------------------------------------
>
>                 Key: CAMEL-3448
>                 URL: https://issues.apache.org/jira/browse/CAMEL-3448
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 2.0.0, 2.1.0, 2.2.0, 2.3.0, 2.4.0, 2.5.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Critical
>             Fix For: 2.6.0
>
>
> If you have a clash with route scoped onException and have the exact same class, then the key in the map isn't catering for this. And thus a 2nd route could override the 1st route onException definition.
> For example:
> from X route A
>   onException IOException
> from Y route B
>   onException IOException
> The map should contain 2 entries, but unfortunately it only contain 1. This only happens when its an exact type match.

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

[jira] Resolved: (CAMEL-3448) Exception policies stores in ErrorHandlerSupport should include route id in key

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CAMEL-3448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-3448.
--------------------------------

    Resolution: Fixed

trunk: 1051239.

> Exception policies stores in ErrorHandlerSupport should include route id in key
> -------------------------------------------------------------------------------
>
>                 Key: CAMEL-3448
>                 URL: https://issues.apache.org/jira/browse/CAMEL-3448
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 2.0.0, 2.1.0, 2.2.0, 2.3.0, 2.4.0, 2.5.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Critical
>             Fix For: 2.6.0
>
>
> If you have a clash with route scoped onException and have the exact same class, then the key in the map isn't catering for this. And thus a 2nd route could override the 1st route onException definition.
> For example:
> from X route A
>   onException IOException
> from Y route B
>   onException IOException
> The map should contain 2 entries, but unfortunately it only contain 1. This only happens when its an exact type match.

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