On Fri, Oct 5, 2012 at 4:23 PM, Claus Ibsen wrote:
> On Thu, Oct 4, 2012 at 12:56 PM, Tim Dudgeon wrote:
>> Thanks, Got it working with a Processor.
>> start() seems to be called twice. Is this expected?
>>
>
> You can extend ServiceSupport then it keeps track of its state. Then
> use the doStart
On Thu, Oct 4, 2012 at 12:56 PM, Tim Dudgeon wrote:
> Thanks, Got it working with a Processor.
> start() seems to be called twice. Is this expected?
>
You can extend ServiceSupport then it keeps track of its state. Then
use the doStart / doStop methods.
> Is it possible to use this for beans? It
Thanks, Got it working with a Processor.
start() seems to be called twice. Is this expected?
Is it possible to use this for beans? It seems not?
e.g. if a route has this
.bean(new MyBean(), 'foo')
and MyBean implements Service then the start() method is not called. So
using a Processor is the on
On Tue, Oct 2, 2012 at 3:38 PM, Tim Dudgeon wrote:
> Are there any tricks or patterns to use when it comes to needing to manage
> the lifecyle of components used in Camel routes.
> For instance if I write a custom Processor that creates something like a
> PreparedStatement how can I make sure its
Are there any tricks or patterns to use when it comes to needing to
manage the lifecyle of components used in Camel routes.
For instance if I write a custom Processor that creates something like a
PreparedStatement how can I make sure its is close()'d when the
CamelContext shuts down.
Thanks
T
