Hey, I'm making a context where I will pickup an Excel file, process it and write it back to disk. I first played around with one route, like this:
<route> <from uri="file:/tmp/meerakker/in"/> <to uri="tika:input=file"/> <to uri="file:/tmp/meerakker/tika"/> </route> Everything works nicely, my custom 'tika' component can convert the excel file to xml without problems But when I introduce ActiveMQ queues and several routes, things start to go wrong. I expected there are some encoding issues introduced by the use of ActiveMQ. So as a test I removed my custom tika component and see what the behaviour was when I just move a excel file from one location to another. Like so: <route> <from uri="file:/tmp/meerakker/in"/> <to uri="activemq:test_in"/> </route> <route> <from uri="activemq:test_in"/> <to uri="file:/tmp/meerakker/out"/> </route> The result is surprising when I consume a perfect fine Excel file which I can open with OpenOffice, the moved file can't be opened as a spreadsheet and contains a bunch of crazy stuff. This is the excel file I used as input order.xls <http://camel.465427.n5.nabble.com/file/n5741661/order.xls> and this result.xls <http://camel.465427.n5.nabble.com/file/n5741661/result.xls> is the resulting file after being moved by Camel. Is there anybody who experienced something similar? I would say this seems like a bug? Anybody got a solution? I already tested the file components with several different encodings without any luck. Any help is welcome! BTW: I'm using Camel 2.10.4 on ServiceMix 4.5.1 -- View this message in context: http://camel.465427.n5.nabble.com/Can-t-move-excel-files-correctly-ActiveMQ-bug-tp5741661.html Sent from the Camel - Users mailing list archive at Nabble.com.
