ext2 wrote:
Thanks Willem:
I got it; and using this feature I could define custom transaction range in
a single route(need not separate them in different route just for
transaction purpose);
I just checked the code, the SpringTransactionPolicy is setting a new
TransactionErrorHandler per route , not just wrapping the processor, so
it works per route. If you want to change this , you need to write your
owner TransactionPolicy.
Willem wrote:
No, you can apply the police per processor.
The new added camel-spring-security is based on this camel policy feature.
how to configure such policy using spring? Or just dsl?
Willem
ext2 wrote:
Hi:
Camel policy is very useful to define some custom wrapper features;
But in camel 2.2 , it seems the policy only apply on the whole route; And
it
cannot define a policy on a special processor, is this true?
And does camel 2.x support some mechanism to support define custom
policy for specified processor(not the whole route)?
