Sounds reasonable to me and would fill our use case nicely. I agree it should not derive from IOException. In the WebDAV code where we use the exception idiom most heavily, only about 20% of the exceptions are thrown due to I/O issues, the rest relate to other issues. For example, I feel that a FileNotFoundException is an IOException because it pertains to Files, not because of the concept of Not Found. Resources can be not found or moved temporarily or operations can fail or conflict for many reasons that involve no I/O whatsoever.
- R
