Apologies to all who bothered. Having read the documentation again, I found out that events such as onUploadStart and onUploadEnd are generated by the DefaultFTPlet. So when I created my FTPlet by directly implementing the interface the methods had to be not called at all. Now that I derive from DefaultFTPlet I get the methods called.
But the other question is still valid: How would my code communicate to the outside world that something is not ok? Raising an Exception is no solution. Do I have to write something like in HttpServlets to the ftpResponse? Do I have to modify the method's return value? Hiran Hiran Chaudhuri System Support Programmer / Analyst IT Service Assurance Hosting & Regional Services (IH) Amadeus Data Processing GmbH Berghamer Strasse 6 85435 Erding T: +49-8122-43x3662 [email protected] http://www.amadeus.com From: Niklas Gustavsson <[email protected]> To: [email protected] Date: 24-06-10 15:38 Subject: Re: Enrich error messages On Thu, Jun 24, 2010 at 3:21 PM, Hiran Chaudhuri <[email protected]> wrote: > So how would I do it from the FTPlet (probably in methods onUploadStart/onUploadEnd)? > And how come I can upload files and see onUploadEnd being not called at all? Yes, onUploadStart() would be a good place to start. If the upload is successful, you should definitely see onUploadEnd being called if the Ftplet is set up correctly. If not, please share your code and test case and we'll have a look at the details. /niklas
