[
https://issues.apache.org/activemq/browse/CAMEL-1532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-1532:
-------------------------------
Description:
The InterceptorStrategy will wrap each node with the interceptor of choice.
This works fine when its needed such as:
- tracer
- delayer
- StreamCacheInterceptor
But sometimes its sufficient to only wrap one time, in the start such as
- UnitOfWork
- Transaction policy
Currently the UnitOfWork is registering itself when all the from is created as
event driven consumers.
We could have a similar list of one-shot interceptors etc. that gets registered
here.
This allows the route path to only contain the needed interceptors instead of
being added around each node.
was:
The InterceptorStrategy will wrap each node with the interceptor of choice.
This works fine when its needed such as:
- tracer
- delayer
But sometimes its sufficient to only wrap one time, in the start such as
- UnitOfWork
- Transaction policy
- StreamCacheInterceptor
This allows the route path to only contain the needed interceptors instead of
being added around each node.
> InterceptStrategy - add feature to only wrap once
> -------------------------------------------------
>
> Key: CAMEL-1532
> URL: https://issues.apache.org/activemq/browse/CAMEL-1532
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-core
> Affects Versions: 2.0-M1
> Reporter: Claus Ibsen
> Fix For: 2.1.0
>
>
> The InterceptorStrategy will wrap each node with the interceptor of choice.
> This works fine when its needed such as:
> - tracer
> - delayer
> - StreamCacheInterceptor
> But sometimes its sufficient to only wrap one time, in the start such as
> - UnitOfWork
> - Transaction policy
> Currently the UnitOfWork is registering itself when all the from is created
> as event driven consumers.
> We could have a similar list of one-shot interceptors etc. that gets
> registered here.
> This allows the route path to only contain the needed interceptors instead of
> being added around each node.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
