Hi Martin, for me the question was, is a 404 really an exception or something more usual. To correct myself: Of course an exception should be thrown. But if we agree that a 404 is a usual respose it would be more easy for a user if it were a special exception such as ResourceNotFoundException.
Unless people want such a special exception, we should leave it as it is, as HttpException covers that case. Regards, Ingo > > From: Ingo Brunberg [mailto:[EMAIL PROTECTED] > > > > The "normal" way of creating a new Resource would be to first create a > > WebdavResource of an existing URL, usually the top-level resource, and > > then call resource.putMethod("newPath", "this is my data"). > > > > Anyway, throwing an exception doesn't seem quite right. I guess this > > change was introduced to inform the user that something went wrong. In > > contrast to most of the methods in WebdavResource, propfindMethod() > > returns an Enumeration instead of a boolean. This means the old > > behavior gives you an empty Enumeration, so it doesn't become apparent > > that the resource does not exist. > > > > The more I deliberate about this, the more I tend to revert the > > change, because you can always query the status code of the > > WebdavResource. > > What do others think about this? > > > > Ingo, for my it does not matter if a exception is thrown or not. But it is > important that all methods have the same behavior. Either the user has to > catch exceptions or check the status code. We could add a member > 'isLastStatusCodeError()'. > > Where do you see the disadvantages of throwing exceptions? > > Martin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
