Forgot to mention: when I inspect the exchange that is expected to contain the grouped N lines from the file that is being processed, I see that Camel inserts the actual regex string I provided to the tokenizer between the lines from the file! The exchange message looks like this:
"[Message: linefromFile1*\r|\r\n|\n*lineFromFile2*\r|\r\n|\n*LineFromFile3*\r|\r\n|\n*...etc] The sequence replace the original line separators. This seems to be a bug, shouldn't be happening. -- View this message in context: http://camel.465427.n5.nabble.com/correct-way-to-provide-regex-in-TokenizerExpression-tp5773192p5773216.html Sent from the Camel - Users mailing list archive at Nabble.com.
