camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (CAMEL-3149) Expose some FileOperations related methods to enable external use (e.g. by Processors)
Date Thu, 23 Sep 2010 13:32:41 GMT

     [ https://issues.apache.org/activemq/browse/CAMEL-3149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Claus Ibsen resolved CAMEL-3149.
--------------------------------

    Fix Version/s: 2.5.0
       Resolution: Fixed

trunk: 1000459.

> Expose some FileOperations related methods to enable external use (e.g. by Processors)
> --------------------------------------------------------------------------------------
>
>                 Key: CAMEL-3149
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-3149
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core, camel-ftp
>            Reporter: Lorrin Nelson
>            Assignee: Claus Ibsen
>             Fix For: 2.5.0
>
>         Attachments: 0001-Make-some-file-operation-related-methods-public-for-.patch
>
>
> Currently writing a Processor to e.g. delete a file on an FTP endpoint requires explicitly
coding for a specific implementation:
>        RemoteFileOperations<ChannelSftp.LsEntry> ops = new SftpOperations();
>        ops.setEndpoint(endpoint);
> This could be avoided by making createRemoteFileOperations() a public (rather than protected)
member of the RemoteFileEndpoint interface?
> Along those lines there's a lot of useful logic in GenericFileProducer.createFileName()
that would be useful when using the file operations directly.
> See email discussion w/ Claus Ibsen on dev@ Sept 2,7,9.
> Proposed patch makes those methods as well as a few others public.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message