[
https://issues.apache.org/activemq/browse/SMXCOMP-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Heinemann resolved SMXCOMP-55.
-----------------------------------
Resolution: Fixed
Fixed the problem.
You got now an attribute overwrite as well to control if existing files will be
overwritten or not.
The endpoint logic is now very similar to the ftp one. Tested it here with
binaryfilemarshaler and it worked fine.
@Ron
Could you verify it is working for you?
> Add get/setTempFileName methods to DefaultFileMarshaler and use in File/Ftp
> Sender Endpoints (also deprecate FTP Sender uploadPrefix/Suffix properties)
> -------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: SMXCOMP-55
> URL: https://issues.apache.org/activemq/browse/SMXCOMP-55
> Project: ServiceMix Components
> Issue Type: Improvement
> Components: servicemix-file, servicemix-ftp
> Affects Versions: 3.2.3
> Reporter: Ron Gavlin
> Assignee: Lars Heinemann
> Fix For: servicemix-file-2009.01
>
> Attachments: SMXCOMP-55.patch
>
>
> The Ftp Sender Endpoint currently has properties uploadPrefix and
> uploadSuffix to allow someone to create a file with a specific "temp"
> prefix/suffix and then rename the file when it is finished being written.
> This would also be useful in the File Sender Endpoint to support scenarios
> where an ftp client is attempting to access a file sender directory and knows
> to avoid reading files with certain "temp" prefixes.
> Since the DefaultFileMarshaler is used by both endpoints, I suggest that
> get/setTempFileName methods be added to the DefaultFileMarshaler and the
> endpoints updated to leverage these methods.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
