I think this should have been taken care of with the https://issues.apache.org/jira/browse/FTPSERVER-222. You might want to try building from the trunk and see if this works out better.
Regards, Sai Pullabhotla On Mon, Mar 29, 2010 at 4:56 AM, Richard Evans (JIRA) <[email protected]> wrote: > Provide more information on command execution to Ftplets - especially file > created in STOU > ------------------------------------------------------------------------------------------ > > Key: FTPSERVER-361 > URL: https://issues.apache.org/jira/browse/FTPSERVER-361 > Project: FtpServer > Issue Type: Improvement > Components: Ftplets > Affects Versions: 1.0.4 > Reporter: Richard Evans > > > To monitor file uploads, I can configure an Ftplet and override onUploadEnd > and onUploadUniqueEnd in DefaultFtplet. However I cannot find a way to > determine the real file that was written in the upload. > > For a non-unique upload I can get the argument and resolve it against the > working directory in the file system view; but this seems unnecessarily > complex and does not for for unique uploads (STOU) because the random file > name is not available. > > Browsing the code I can see the file observer stuff, but these are non-public > APIs and there can be only one observer at a time whilst I can have many > independent Ftplets implementing the onUpload APIs. > > -- > This message is automatically generated by JIRA. > - > You can reply to this email to add a comment to the issue online. > >
