On Mon, Nov 26, 2012 at 4:25 PM, anu_cameluser <[email protected]> wrote: > Claus, > > Thanks for your suggestion - adding noop=true to the file endoint URI > resolved the issue with original file being deleted. > > The first issue with the file received at ftp destination being empty turned > out to be more interesting. With a very small exchange body (just "hello > world body"), the local file was created ok, but remote file was emtpy. When > I changed my test class to create a string atleast 1000 characters long, the > remote file was no longer empty. > > Are there any known issues that camel has with transferring very small > files?
That seems odd. The file is read the same using a FileInputStream. I wonder if you create the file the same way, using same encoding? And does it fail for you every time with a small file? > > Thanks! > Anu > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/File-generation-and-FTP-tp5722795p5723245.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- Red Hat, Inc. FuseSource is now part of Red Hat Email: [email protected] Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
