Well, it turns out that the uploaded files had ONLY the '\r' (x0D) character for the "new line". I was too blind to see - assuming that it could only be either '\n' (UNIX) or "\r\n" (MS Windows.) So, I was staring at 'x0D' not even questioning the fact that it represented '\n', while it is, of course '\r', which my pattern was not checking for. So, I solved the problem by using the following for the tokenizing pattern:
*"\n|\r|\r\n"* This should take care of all cases. (I am still not certain why the files have just "\r" while the valid system-specific NL sequence should be either "\n" or "\r\n".) -- View this message in context: http://camel.465427.n5.nabble.com/splitter-tokenize-does-not-group-lines-from-file-uploaded-using-Spring-MVC-MultipartFile-tp5773127p5773161.html Sent from the Camel - Users mailing list archive at Nabble.com.
