I've found that by doing
from("jms:queue.submiterror").multicast().to("jms:queue.erroremailer" ,
"file://target/test?noop=true");
I can get the messages to both the file and the other queue, but I'm still
curious why it wouldn't do the wiretap without the multicast()?
As for the .processor() that is supposed to transform the errormailer
messages, I still have had no luck in getting it to send anything to another
destination post-processing (be it email, or a file). I've tried modifying
the in message, as well as setting the out message, but no luck.
Cheers,
Jan
jan.pittner wrote:
>
> LOG.info("Configuring route.");
> from("jms:queue.submiterror").
> to("jms:queue.erroremailer" );//,
> "file://target/test?noop=true");
> from("jms:queue.erroremailer").process( new ErrorEmailer()
> );//.to("smtp://[EMAIL PROTECTED]");
>
> I've added the logging to watch what happens in the ErrorMailer:
>
> ErrorMailer::Process
> LOG.info("Processing message.");
> Message in = exchange.getIn();
> ... summarize the message and make it human readable ..
> Message out = exchange.getOut();
> out.setBody(stuff);
> out.setHeader("to", "[EMAIL PROTECTED]");
>
>
--
View this message in context:
http://www.nabble.com/Camel-Noob---processing-in-the-pipeline%2C-logging-tf4862467s22882.html#a13951347
Sent from the Camel - Users mailing list archive at Nabble.com.
