2008/12/11 Claus Ibsen <[EMAIL PROTECTED]>: > Hi > > In lack of a better subject I named it "Triggering scheduled consumers" > > An end user had a very decent question last day that was a bit of a > challenge for me to do nicely in Camel (and still is). > See nabble: > http://www.nabble.com/Trigger-causes-Poll-from-ftp-server-to-sftp-td20934240s22882.html > > The use-case is that he wants to poll a file from a FTP server from > within a route. And how do you do that in Camel? > As the FTP consumer is a scheduled consumer its only to be used in the > from type. > > But he wants to trigger this when a message arrives on a JMS queue > from(jms:queue).XXXXX.to(somewhere else) > where XXX is where we download the file from the FTP server > > I do think that downloading a single file from a FTP server, or > reading a file from a file system should be easy and possible from > within a route. > But for both the FTP consumer and the File consumer they are scheduled > based. And this is because they can by interval scan folders for files > to consume and fire them in the route. > > However reusing these components for a use-case: I need to download a > file or I need to read a file is a valid question that end users of > Camel will raise and try/expect it to be able to. > > So do we have other Camel components where end users might wanna do > something like this? For instance Jon's new RSS component?
Yeah - being able to easily poll an endpoint is required quite often I'd say. Ditto HTTP/FTP and databases too One approach could be we use ExchangePattern? e.g. * InOnly for a File endpoint could write the file. (bit like a HTTP PUT?) * InOut could write and read it back? (bit like a HTTP POST?) * OutOnly could just read the file thats there (bit like a HTTP GET) -- James ------- http://macstrac.blogspot.com/ Open Source Integration http://fusesource.com/
