hmm... I need my direct:MoveUpload b/c it's called from various other routes.
It's a generic route. Is there another way?
One approach might be to filter out the unwanted file. There's no
include/exclude on FTP. I'm using java dsl so can't use ANT filter. I could
use GenericFilter i suppose. But is there a more standard way to deal with
this?
Would it be your suggestion that rather than use
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}}{{move.to.uriparams}}";))
I just use
from("file://{{move.from.dir}}?noop=true")
.recipientList(simple("ftp://{{move.to.user}}@{{move.to.host}}/{{move.to.dir}}?password={{move.to.pwd}}{{move.to.uriparams}}";))
? If so, how would I use this flow as a part of a larger flow, in which i
branch from some other route to this one?
thanks for your time and thoughts.
--
View this message in context:
http://camel.465427.n5.nabble.com/How-to-prevent-ftp-from-creating-ID-file-tp5748344p5748350.html
Sent from the Camel - Users mailing list archive at Nabble.com.
