Actually I would like a more flexible solution, like using some kind of a
strategy or maybe a route policy or something to trigger the commit (I'm
not aware of all mechanisms existing in Camel that might be suiting here).
My use case is not completely defined yet, but something like this:
1. Assu
This is at least "my" requirement.
Sent from a mobile device
Am 07.08.2012 18:47 schrieb "Scott England-Sullivan" :
> Hi Thomas,
>
> It sounds like you are looking for something like the following:
>
> from("sjms:consumer?transacted=true&batch=100")
> .processor("do stuff")
> to("file:output");
>
We try to cut a minor release every 3 month. The last release (2.10.0) was
cut after ~5 month, if I remember right.
This means we doesn't have a fix schedule for it.
Sent from a mobile device
Am 07.08.2012 15:26 schrieb "Scott England-Sullivan" :
> Christian,
>
> What is the proposed cut off dat
Hi Thomas,
It sounds like you are looking for something like the following:
from("sjms:consumer?transacted=true&batch=100")
.processor("do stuff")
to("file:output");
Such that 100 messages would be consumed, processed and filed followed by
the session either being committed or rolled back based
I tried to register to the dev forum and the register page said it is
registering and email sent. But I never received the email for activating my
account.
Thanks,
Gary
Sent from my iPhone
On Aug 7, 2012, at 11:30 AM, Christian Müller
wrote:
> No, it should be possible.
> Which one do you m
I'm not sure what this implies, Scott.
My use case is to have a transaction started on a first exchange, and then have
X exhanges on the same transaction. It should first be committed when some
external event happens, like a control message is seen (possibly from a
separate control queue), afte
No, it should be possible.
Which one do you mean? users, dev, commits?
Which error did you get?
Best,
Christian
On Tue, Aug 7, 2012 at 5:06 AM, Gary Liu wrote:
> Is the Nabble forum closed to new registration? Can anybody help me?
>
> Thanks,
> Gary
>
--
Christian,
What is the proposed cut off date for 2.11?
On Aug 7, 2012, at 6:21 AM, Christian Müller
wrote:
> +1
> Would like to see this feature too...
>
> Sent from a mobile device
> Am 07.08.2012 10:49 schrieb "Thomas Johansen" :
>
>> Hi,
>>
>> As I understand the JMSComponent/ActiveMQCom
I will take a look at it tonight. Plan is to add batch support by having
the Producer and Consumer endpoints support a List of Messages. Once in
place TX would be automatically supported as it is called as a
Synchronization upon completion of the Exchange.
Thoughts?
On Tue, Aug 7, 2012 at 6:21
> Another 20 licenses added in rev904. 50 left to go :) .
Committed next batch (rev905). 20 licenses to go.
--
Henryk Konsek
http://henryk-konsek.blogspot.com
+1
Would like to see this feature too...
Sent from a mobile device
Am 07.08.2012 10:49 schrieb "Thomas Johansen" :
> Hi,
>
> As I understand the JMSComponent/ActiveMQComponent cannot support batched
> transactions due to the use of Spring's DMLC. With this new SJMSComponent
> there should be poss
Hi,
As I understand the JMSComponent/ActiveMQComponent cannot support batched
transactions due to the use of Spring's DMLC. With this new SJMSComponent
there should be possibilities to implement this, I guess?
BR,
Thomas
12 matches
Mail list logo
