Sounds good. This particular feature has already been discussed a few times but never implemented.
A nice thing to do would be to define a WSDL for this endpoint so that it could support more operations (polling for a file, sending a file, listing a folder, renaming, etc...) This contract could be used on all file based components to provide a common interface. I guess we can start by the only operation you need and extend the interface after. Anyway, feel free to ping the dev list about that and provide a patch if you want this feature to be included in ServiceMix. On 7/3/07, rabi <[EMAIL PROTECTED]> wrote:
Hi All, I have a usecase where I have to pull some files from a ftp location based on a trigger. Actually the trigger message will contain the file name and location. -Trigger can be Quartz Trigger (With the message as the payload) or can be triggered by another service. - FTP endpoint will parse the exchange and get the file from the ftp location and send it to the target service configured for this endpoint. - I have configured a quartz endpoint with a CustomMarshaller and can get the message as expected. - I am writting a custom FTPReceiverEndpoint extending ProviderEndpoint (In similar lines of EIPEndpoint) I want to validate the approach and would like to know if there is any better approach available for this. Regards, Rabi -- View this message in context: http://www.nabble.com/Use-Case%3A-FTP-endpoint-Triggered-by-another-Service-tf4017616s12049.html#a11410007 Sent from the ServiceMix - User mailing list archive at Nabble.com.
-- Cheers, Guillaume Nodet ------------------------ Principal Engineer, IONA Blog: http://gnodet.blogspot.com/
