Spring Integration
  1. Spring Integration
  2. INT-1945

Implement (s)ftp Outbound Gateway (ls, get, rm)

    Details

    • Type: New Feature New Feature
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Complete
    • Affects Version/s: 2.0.4
    • Fix Version/s: 2.1 M1
    • Component/s: Adapters
    • Labels:
      None

      Description

      Rather than polling a remote (s)ftp server, it would be useful to be able to perform a flow similar to the following...

      gateway->ls->splitter->get->process->rm

        Issue Links

          Activity

          Hide
          Oleg Zhurakousky added a comment - - edited

          There are some interesting discussions about the need for something like this (on demand, configurable remote operations)
          http://forum.springsource.org/showthread.php?110125-Sftp-outbound-to-multiple-destinations
          http://forum.springsource.org/showthread.php?112086-Inbound-FTP-Polling-sub-directories&p=371633&posted=1#post371633

          Although currently we have a clear pattern within SI where each and every gateway/adapter is a static "addressable" component (and there are many reasons for it), so an alternative approach would be to create a RemoteFileTemplate which also fits Spring paradigm.
          In other words we have to make a decision. Either we stand by our position that "adapters are addressable endpoints" while *Templates can be used for dynamic situations, OR we make some big changes in 2.1+ so that adapters can indeed have multiple addresses that are dynamically determined at runtime.

          Show
          Oleg Zhurakousky added a comment - - edited There are some interesting discussions about the need for something like this (on demand, configurable remote operations) http://forum.springsource.org/showthread.php?110125-Sftp-outbound-to-multiple-destinations http://forum.springsource.org/showthread.php?112086-Inbound-FTP-Polling-sub-directories&p=371633&posted=1#post371633 Although currently we have a clear pattern within SI where each and every gateway/adapter is a static "addressable" component (and there are many reasons for it), so an alternative approach would be to create a RemoteFileTemplate which also fits Spring paradigm. In other words we have to make a decision. Either we stand by our position that "adapters are addressable endpoints" while *Templates can be used for dynamic situations, OR we make some big changes in 2.1+ so that adapters can indeed have multiple addresses that are dynamically determined at runtime.

            People

            • Assignee:
              Gary Russell
              Reporter:
              Gary Russell
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: