Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (athena.apache.org: domain of claus.ibsen@gmail.com
 designates 209.85.219.53 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAKoNANsMf_38v+X7p_FfDHEb8H23L0gfz_q3_1bnapfX7e8=fg@mail.gmail.com>
References: <1364303596339-5729849.post@n5.nabble.com>
 <CAGB5yNnNnU8B0NdxRWsXDwQnkQhjsOZWd_sc6dw0gRhg2jG9RA@mail.gmail.com>
 <CALvzYd9yR5DXWNy+6_u9KFjBb=FqNYQTQSrs=feac_oEthV5vQ@mail.gmail.com>
 <CAGB5yNnq5M81V7gd0JLKyktQGcBKMebb2d=u0NngMO7ZJHtfkQ@mail.gmail.com>
 <CAKoNANsMf_38v+X7p_FfDHEb8H23L0gfz_q3_1bnapfX7e8=fg@mail.gmail.com>
From: Claus Ibsen <claus.ibsen@gmail.com>
Date: Thu, 28 Mar 2013 12:25:28 +0100
Message-ID: 
 <CAGB5yNnR4QovcN-iT7CRBroGqchfo=B06-7QrVfRZd7SyrvXVw@mail.gmail.com>
Subject: Re: Clearing ThreadLocal when exchange completes
To: users@camel.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Thu, Mar 28, 2013 at 9:36 AM, Raul Kripalani <raul@evosent.com> wrote:
> With this technique, developers  have to remember to add the custom
> processor at the start of each route. (Unless it's set from an
> interceptor...).
>
> Since the user explicitly asked for a non intrusive technique,
> EventNotifier is the only method that fulfills that requirement. Set once
> per Camel context and forget about it.
>
> And it's higher level, not fiddling with internal APIs.
>

That would only work if its the same thread that calls the listener at
exchange created and exchange done events. As he need to use that same
thread for clearing his thread locals.


> Just my 2 cents.
>
> Regards,
> Ra=FAl.
>  On 28 Mar 2013 06:11, "Claus Ibsen" <claus.ibsen@gmail.com> wrote:
>
>> On Wed, Mar 27, 2013 at 10:02 PM, Christian M=FCller
>> <christian.mueller@gmail.com> wrote:
>> > Isn't it called in a separate thread, isn't it?
>> >
>>
>> Ah yeah, then use this as base class
>>
>> http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/came=
l/support/SynchronizationAdapter.html
>>
>> And return false from the allowHandover method
>> Then its done on the same thread.
>>
>>
>> > Sent from a mobile device
>> > Am 27.03.2013 08:14 schrieb "Claus Ibsen" <claus.ibsen@gmail.com>:
>> >
>> >> You can use this method on the Exchange
>> >>
>> >>
>> >>
>> http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/came=
l/Exchange.html#addOnCompletion(org.apache.camel.spi.Synchronization)
>> >>
>> >>
>> >> On Tue, Mar 26, 2013 at 2:13 PM, davelund <david.r.lund@gmail.com>
>> wrote:
>> >> > We are currently using ThreadLocal to store some information that g=
ets
>> >> > included in a log4j converter (and is used in other projects that d=
ont
>> >> have
>> >> > camel in). Is there a callback I can use that for all routes in my
>> >> context
>> >> > so that at the end of the route it will get called (without explici=
tly
>> >> > setting it) For example:
>> >> > from("jms:somequeue")
>> >> >   .processRef("someRandomProcessor")
>> >> >   .processRef("someProcessorThatSetsThreadLocalValue")
>> >> >   ....
>> >> >   .to("jms:someotherqueue")
>> >> >
>> >> >
>> >> > Ideally I'd like the threadlocal cleared when the exchange has been
>> >> written
>> >> > to the queue, without adding a processor that explicitly clears it =
(as
>> >> > developers when adding new routes will forget to do it). I know the
>> >> > onCompletion runs in a seperate thread so isn't fit for my purpose.
>> I've
>> >> > noticed  syncronisations and unitofworks, but cant seem to find any
>> >> > documentation on it. Would this be fit for purpose?
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > View this message in context:
>> >>
>> http://camel.465427.n5.nabble.com/Clearing-ThreadLocal-when-exchange-com=
pletes-tp5729849.html
>> >> > Sent from the Camel - Users mailing list archive at Nabble.com.
>> >>
>> >>
>> >>
>> >> --
>> >> Claus Ibsen
>> >> -----------------
>> >> Red Hat, Inc.
>> >> FuseSource is now part of Red Hat
>> >> Email: cibsen@redhat.com
>> >> Web: http://fusesource.com
>> >> Twitter: davsclaus
>> >> Blog: http://davsclaus.com
>> >> Author of Camel in Action: http://www.manning.com/ibsen
>> >>
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> Red Hat, Inc.
>> FuseSource is now part of Red Hat
>> Email: cibsen@redhat.com
>> Web: http://fusesource.com
>> Twitter: davsclaus
>> Blog: http://davsclaus.com
>> Author of Camel in Action: http://www.manning.com/ibsen
>>


--=20
Claus Ibsen
-----------------
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cibsen@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen