On Wed, Jun 8, 2011 at 12:55 PM, Allen Firstenberg
<[email protected]> wrote:
> The "logging" in this case isn't code level logging, it is command/transfer
> logging.  It is an ftplet that can be configured to log various attributes
> from an FtpSession, FtpRequest, and/or FtpReply.  It is intended for xferlog
> and similar logging capabilities.  We've mentioned this in the past as
> something we're working on and that we intend to release to the project when
> we feel its ready for prime time.

Sorry, I forgot the basic problem you described. I've reviewed our
code, and fail to find a way that Ftplet.beforeCommand() would not be
called. Ftplet.afterCommand() could of course we skipped if
beforeCommand returns SKIP or the command itself throws an exception.
But, I guess you already checked this.

If I understood correctly this happens very infrequently and with no
possibility of reproducing?

/niklas

Reply via email to