can also just have a from direct and then from whatever bean you
have send a message to that direct endpoint for Camel route.
On Wed, Nov 20, 2013 at 9:00 PM, flovansi [hidden
email]/user/SendEmail.jtp?type=nodenode=5743588i=0 wrote:
I m not sure it'll be possible with the @Consume
Hi all,
Is it possible to consume message from a Java bean?
Something like:
from ref=myBean/
where myBean could be a custom bean to get JMS message from a queue, or
anything you can think of.
I know that I can achieve that by creating custom Camel Component but a Java
Bean could be simpler in
You dont need a route if you use a pojo with the @Consume annotation
as shown in that example.
On Wed, Nov 20, 2013 at 5:29 PM, flovansi lt; [hidden email] gt; wrote:
gt; Hi all,
gt;
gt; Is it possible to consume message from a Java bean?
gt;
gt; Something like:
gt;
gt; lt;from ref=quot
Jira ticket has been
created:https://issues.apache.org/jira/i#browse/CAMEL-6863
--
View this message in context:
http://camel.465427.n5.nabble.com/SJMS-implementation-Batch-Consumer-tp5741291p5741581.html
Sent from the Camel Development mailing list archive at Nabble.com.
These tests requires manual intervention (looking if messages are still in
the queue or are they committed?). But these are simple tests that proves
the batch transaction support offered by SJMS is not 100% correct
(especially the behaviour of the timeout!!!).
--
View this message in context:
Yes I understand the purpose of the timeout but what if an exchange has just
been read by the SJMS consumer and the timeout is triggered? The processing
of the timeout commits the transaction while the exchange could still be
inflight and could fail.
In general, the commit of the transaction
Thank you for your answer.
I do not have any unit tests right now but I'll try to do some.
Another thing that is strange in the implementation of the timeout.
The timeout is set in the resetTask() method which is called at the
completion of the exchange
Here are some test cases.
@Test
//The timeout is set in the resetTask() method which is called at the
completion of the exchange (SessionBatchTransactionSynchronization.java).
//If I'm understanding it well, the timeout seems to be reset at each
exchange completion.
//That is not
Hi,
I’m interested in the feature “Batch Consumer” offered by SJMS.
By looking at the code, I noticed that the commit of the JMS session is done
in the completion of the last exchange of the batch
(/org.apache.camel.component.sjms.tx.SessionBatchTransactionSynchronization.java/)
Does SJMS
