Thank you.
--
View this message in context:
http://www.nabble.com/Dynamic-RecipientList-delimeter-issue-tp25917854p26067821.html
Sent from the Camel - Users mailing list archive at Nabble.com.
We upgraded from Camel 1.5 to 2.0 and realized that the default behavior of
RecipientList has changed. Even though in 2.0, we can specify a delimiter,
comma is always considered as a delimiter on top of what ever we specified
as our custom delimiter.
Is there a way to make it ignore commas in th
Thanks Claus. Do you know when is Camel 2.0 scheduled to be released?
--
View this message in context:
http://www.nabble.com/Problem-with-IdempotentConsumer-tp22467720p22482175.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi,
Below is from IdempotentConsumer.java of Camel 1.5:
public void process(Exchange exchange) throws Exception {
String messageId =
ExpressionHelper.evaluateAsString(messageIdExpression, exchange);
if (messageId == null) {
throw new NoMessageIdException(exchange, mes
I just realized that we need to use
"org.springframework.jms.connection.CachingConnectionFactory". As of spring
2.5.6, this supports caching of connection/sessions/consumers/producers and
is strongly recommended to use with JmsTransactionManager!
--
View this message in context:
http://www.nabbl
May be we shoud use CACHE_NONE when using JmsTransactionManager so that it
creates a new connection/session/consumer for every message? That's bad!
--
View this message in context:
http://www.nabble.com/JmsComponent-issue-with-spring%27s-JmsTransactionManager-is-used-tp21697364s22882p21698182.ht
Hi,
It seems to me that Spring's DMLC implementation has a flaw/bug when
JmsTransactionManager and CACHE_SESSION is used. It seems, spring is
creating a session upfront once as we have cache session and a new session
for every message in JmsTransactionManager. The cached session is being used
fo
