Thanks for reporting! I've fixed this issue in trunk. I haven't
checked but I believe I introduced it in a recent refactoring. We
really need more test cases for Ftplets :-(

So, now you can do this again in a Ftplet:
        session.write(new DefaultFtpReply(550, "Bad bad client!"));
        return FtpletEnum.RET_SKIP;

/niklas

On Thu, Aug 7, 2008 at 4:36 PM, Jeroen Cranendonk
<[EMAIL PROTECTED]> wrote:
> Hi!
>
> I think this should be easy, but with the current code I can't figure it out
> :)
>
> How does on return say a 550 + message from a ftplet?
>
> In the old code you had an object available in the ftplet you could call
> write(FtpReply(..)) on, and combined with a SKIP return code, that would do
> the trick.
>
> In the current code I can't find anything to do that, help ? :)
>
>
> A example of a Ftplet with some basic demo functionality would be pretty
> usefull :)
>
> Thanks!
> Jeroen
>
>
>
> _______________________________________________________________________________________________
> Help save paper! Do you really need to print this email?
>
> Aan de inhoud van dit bericht kunnen alleen rechten ten opzichte van Sdu 
> Identification B.V.
> worden ontleend, indien zij door rechtsgeldig ondertekende stukken worden 
> ondersteund.
> De informatie in dit e-mailbericht is van vertrouwelijke aard en alleen 
> bedoeld voor gebruik
> door geadresseerde. Als u een bericht onbedoeld heeft ontvangen, wordt u 
> verzocht de
> verzender hiervan in kennis te stellen en het bericht te vernietigen zonder 
> te vermenigvuldigen
> of andersoortig te gebruiken.
>
> The contents of this electronic mail message are only binding upon Sdu 
> Identification B.V.,
> if the contents of the message are accompanied by a lawfully recognized type 
> of signature.
> The contents of this electronic mail message are privileged and confidential 
> and are intended
> only for use by the addressee. If you have received this electronic mail 
> message by error,
> please notify the sender and delete the message without reproducing it and 
> using it in any way.
>
>

Reply via email to