Steve Ulrich wrote:
Hi!
Niklas Gustavsson [mailto:[EMAIL PROTECTED] wrote
Yes, I'm aware that we can chain and replace exceptions thrown by the
various protocols, that was not my concern. My question was if
IOExceptions semantics matches the error conditions that we talk about
here. From the Javadoc: "Signals that an I/O exception of some sort
has occurred". I'm not sure if this is true for many of the cases
where the FtpServer file system abstraction fails. But then again,
this might be a case of splitting hairs. What do the rest of you
think?
Using IOException for anything not IO related isn't a good practice. If there's
really an IOException the implementation must cleanup the IO resources!
Misusing IOException will lead to confusion and zombie connections/IO resources.
I totally agree.
--
--
cordialement, regards,
Emmanuel Lécharny
www.iktek.com
directory.apache.org
