Bruce Do you want to manually inspect files and copy files to some other area for replay ?
Are you not using any messaging channel queue to store messages ? You can use dumpAsXml to inspect the content but use the messaging channel queue again to replay the messages. Some custom filter can be developed on this message queue which will filter message based on message ids. [These message id(s) can be entered by you in a file after manually inspecting xml file message] - Ravi ________________________________________ From: bhcohen [bruce_co...@sra.com] Sent: Monday, January 27, 2014 11:03 PM To: users@camel.apache.org Subject: MessageHelper.dumpAsXml() Since MessageHelper.dumpAsXml() marshals a Message as XML, is there a method somewhere that does the opposite, i.e. takes XML output generated by from dumpAsXml() and produces a Message? I'm trying to implement a dead letter channel in which I write problematic Messages (body and header) to a file so that they can be examined but then later replayed through Camel. I'd like to avoid implementing my own file format, dumpAsXml() appears to meet my needs for persisting headers and body but I'm not sure if there is a way take the output of dumpAsXml() and have it parsed into headers and body and sent to an endpoint. Any guidance would be greatly appreciated. -Bruce -- View this message in context: http://camel.465427.n5.nabble.com/MessageHelper-dumpAsXml-tp5746505.html Sent from the Camel - Users mailing list archive at Nabble.com. This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient(s), please reply to the sender and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email, and/or any action taken in reliance on the contents of this e-mail is strictly prohibited and may be unlawful.
