Just committed a fix that should make this go away. The
DefaultExchange.copy() can now deal with null messages.
On 4/19/07, dr.jeff <[EMAIL PROTECTED]> wrote:
When I do this:
from("queue:a").to("queue:b", "queue:c");
from("queue:b").process(new StringProcessor());
I get this:
2007-04-19 12:28:12,616 ERROR [org.apache.camel.processor.DeadLetterChannel]
- On delivery attempt: 1 caught: java.lang.NullPointerException
java.lang.NullPointerException
at
org.apache.camel.impl.DefaultExchange.copyFrom(DefaultExchange.java:59)
...
--
View this message in context:
http://www.nabble.com/-camel--Splitter-problem-tf3609288s2354.html#a10085314
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
--
Regards,
Hiram
Blog: http://hiramchirino.com
