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 2011/04/17 17:31:05 UTC
[jira] [Updated] (CAMEL-3870) Add support for setting onException,
interceptors etc in routeContext (reusable onexceptions)
[ https://issues.apache.org/jira/browse/CAMEL-3870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen updated CAMEL-3870:
-------------------------------
Component/s: camel-spring
camel-core
Fix Version/s: 2.9.0
Summary: Add support for setting onException, interceptors etc in routeContext (reusable onexceptions) (was: reusable onexceptions)
> Add support for setting onException, interceptors etc in routeContext (reusable onexceptions)
> ---------------------------------------------------------------------------------------------
>
> Key: CAMEL-3870
> URL: https://issues.apache.org/jira/browse/CAMEL-3870
> Project: Camel
> Issue Type: Improvement
> Components: camel-core, camel-spring
> Reporter: Kris De Schutter
> Fix For: 2.9.0
>
>
> Cfr. http://camel.465427.n5.nabble.com/reusable-onexceptions-td4304909.html
> I can reuse route definitions by putting them in a <routeContext> and then referring to them. I would like to do the same with <onException> definitions.
> The context I'm working in is one where we define routes by composing reusable route definitions. This works well, but I find that we have to duplicate the more general <onException> handlers. I was hoping that I could reuse their definitions as well.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira