Thank you very much for your help.
While waiting your bug fix, reading the source code, I tried successfully the
patch to the method sessionOpened of the
class org.apache.ftpserver.impl.DefaultFtpHandler.
I made the following patch: public void sessionOpened(final FtpIoSession
session) throws Exception {
FtpletResult ftpletRet =
context.getFtpletContainer().onConnect(session.getFtpletSession());
if (ftpletRet == FtpletResult.DISCONNECT) {
session.close(false).awaitUninterruptibly(10000); return; }
session.updateLastAccessTime();
session.write(LocalizedFtpReply.translate(session, null, context,
FtpReply.REPLY_220_SERVICE_READY, null, null)); }
I hope this can help you somehow.
let me know if this can help you.
Thank you again.
Massimiliano.
Massimiliano
--- Mer 13/5/09, Niklas Gustavsson <[email protected]> ha scritto:
Da: Niklas Gustavsson <[email protected]>
Oggetto: Re: (custom Ftplet) onConnect method problem
A: [email protected]
Data: Mercoledì 13 maggio 2009, 21:00
On Wed, May 13, 2009 at 5:01 PM, Sai Pullabhotla
<[email protected]> wrote:
> This appears to be a bug in the FtpServer where it is ignoring the return
> value from the Ftplet(s). Can some one else confirm too?
Agreed. I will work on a fix tonight that will be available in 1.0.1
that I hope to put up for voting in the next few days.
/niklas
