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'm afraid you cannot configure the transaction per process, as Camel
transaction is based on Spring, and it uses thread location to hold the
transaction information. You may need to do something yourself to
implement the feature.
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)?
