You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2012/09/25 09:39:07 UTC
[jira] [Created] (CAMEL-5647) EIPs using custom aggregation
strategy should fail if not possible to find in registry
Claus Ibsen created CAMEL-5647:
----------------------------------
Summary: EIPs using custom aggregation strategy should fail if not possible to find in registry
Key: CAMEL-5647
URL: https://issues.apache.org/jira/browse/CAMEL-5647
Project: Camel
Issue Type: Bug
Components: camel-core, eip
Affects Versions: 2.10.0, 2.9.0
Reporter: Claus Ibsen
Assignee: Claus Ibsen
Fix For: 2.9.4, 2.11.0, 2.10.2
Some EIPs support using a custom aggregations strategy. And if you use XML DSL to refer to a custom strategy, then you may have typo, or the strategy do not implement the interface.
What we should do is to ensure to fail if the custom strategy could not be looked up.
Some EIPs such as the content enricher will fallback and use a default strategy. This is wrong.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CAMEL-5647) EIPs using custom aggregation
strategy should fail if not possible to find in registry
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-5647.
--------------------------------
Resolution: Fixed
> EIPs using custom aggregation strategy should fail if not possible to find in registry
> --------------------------------------------------------------------------------------
>
> Key: CAMEL-5647
> URL: https://issues.apache.org/jira/browse/CAMEL-5647
> Project: Camel
> Issue Type: Bug
> Components: camel-core, eip
> Affects Versions: 2.9.0, 2.10.0
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.9.4, 2.11.0, 2.10.2
>
>
> Some EIPs support using a custom aggregations strategy. And if you use XML DSL to refer to a custom strategy, then you may have typo, or the strategy do not implement the interface.
> What we should do is to ensure to fail if the custom strategy could not be looked up.
> Some EIPs such as the content enricher will fallback and use a default strategy. This is wrong.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira