You route has 2 inputs, remove the direct:moveUpload so it only has one. Its when you call that input the file name is empty and you get that empty file with the message id as its name.
On Wed, Mar 5, 2014 at 5:33 PM, mister blinky <[email protected]> wrote: > I have a route that uploads files in a directory to a remote server. It > determines *what* and *where* to upload at runtime using properties, so it > uses a recipientlist. > > from("direct:moveUpload") > .log("@@@ MoveUpload: Using properties: " + propsId) > .from("file://{{move.from.dir}}?noop=true") > > .recipientList(simple("ftp://{{move.to.user}}@{{move.to.host}}/{{move.to.dir}}?password={{move.to.pwd}}";)) > > So it copies all the files in the move.from.dir directory to the server as > expected, but it also creates an empty file > ID-<myserver>-59340-1394036464705-0-1. I don't want this empty file. > > From reading the doc, it would seem to be created by the file component when > CamelFileName is null. But why would any file in this directory be unnamed? > There are no hidden files. All the files are properly transferred, but this > ID- file gets generated and then transferred as well. > > How can i prevent ftp from creating that empty ID- file? > > thank you. > > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/How-to-prevent-ftp-from-creating-ID-file-tp5748344.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- Red Hat, Inc. Email: [email protected] Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen Make your Camel applications look hawt, try: http://hawt.io
