Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (nike.apache.org: domain of claus.ibsen@gmail.com
 designates 209.85.218.228 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type:content-transfer-encoding;
        b=kfgDwFh+d6/16i0OdW5eokhz2evSXOk6YPYAiqzavEc/J23vXaCkWH9j9UyBxROsqi
         Ows8yTfcTKSopagSTkSrlAb4S7SHcBhm5ofvW/Ur993RFheEQI1SvFi61kIsyqSTmQsH
         5OUX7zoumbte1tTdWddVwgHsZ/WB5k8pZmw2Y=
MIME-Version: 1.0
In-Reply-To: <81EB3BA5959A4B749893D377DFF80206@IBM0618>
References: <81EB3BA5959A4B749893D377DFF80206@IBM0618>
From: Claus Ibsen <claus.ibsen@gmail.com>
Date: Thu, 22 Apr 2010 14:24:00 +0200
Message-ID: <l2v5380c69c1004220524tb87d2ab4j48650f411ecaf6f3@mail.gmail.com>
Subject: Re: does camel support custom policy for processor level ?
To: users@camel.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi

I am opening up this in Camel 2.3.0 so you can use Policy at per
processor level.

I have created a ticket to track it
https://issues.apache.org/activemq/browse/CAMEL-2667


On Thu, Apr 22, 2010 at 9:45 AM, ext2 <xuhb@tongtech.com> wrote:
>
>
> Thanks Willem:
>
> You are right;
> =A0It seems I must do something else to support the feature(define custom
> transaction-section in single route).
>
> And the real problem is not only the spring's transaction-template, but a=
lso
> the camel's transaction support ;
> =A0the camel's transaction always ask for transacted-error-handler, and t=
hey
> will sometimes conflict with other error-handle mechanism(etc: try-catch)=
;
>
>
> Willem wrote;
>>>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:
>>> =A0 =A0 =A0Camel policy is very useful to define some custom wrapper fe=
atures;
>>> But in camel 2.2 , it seems the policy only apply on the whole route; A=
nd
>> it
>>> cannot define a policy on a special processor, is this true?
>>> =A0 =A0 =A0And does camel 2.x support some mechanism to support define =
custom
>>> policy for specified processor(not the whole route)?
>>>
>>>
>>>
>>
>>
>>
>>
>>
>>
>
>
>
>


--=20
Claus Ibsen
Apache Camel Committer

Author of Camel in Action: http://www.manning.com/ibsen/
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus