You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Lorrin Nelson (JIRA)" <ji...@apache.org> on 2010/09/23 02:35:40 UTC
[jira] Created: (CAMEL-3149) Expose some FileOperations related
methods to enable external use (e.g. by Processors)
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
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.
[jira] Assigned: (CAMEL-3149) Expose some FileOperations related
methods to enable external use (e.g. by Processors)
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-3149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen reassigned CAMEL-3149:
----------------------------------
Assignee: Claus Ibsen
> 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
> 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.
[jira] Updated: (CAMEL-3149) Expose some FileOperations related
methods to enable external use (e.g. by Processors)
Posted by "Lorrin Nelson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-3149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lorrin Nelson updated CAMEL-3149:
---------------------------------
Attachment: 0001-Make-some-file-operation-related-methods-public-for-.patch
> 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
> 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.
[jira] Resolved: (CAMEL-3149) Expose some FileOperations related
methods to enable external use (e.g. by Processors)
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ 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.