2008/10/2 Emmanuel Lecharny <[EMAIL PROTECTED]>: > Andrea Francia wrote: >> >> 2008/10/2 Steve Ulrich <[EMAIL PROTECTED]>: >> >>> >>> 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. >>> >> >> I/O mean input/oputput, it does not cover only the I/O to real >> filesystem it cover also I/O trough the net sockets, the >> RemoteException used in RMI is an IOException. >> > > That does not mean FtpException should not inherit from IoException. This is > also an option. I'm not proposing that however.
-- Andrea Francia http://andreafrancia.blogspot.com/
