> I had the same problem with TC 321.
> I have applied a patch within a jar file. If you add this to your
classpath,
> right before webserver.jar, the exception (which is harmless as said by
> Remy) will dissappear.
> In my environment it was sufficient to copy the jar file to the Tomcat lib
> directory.
I thought they had added the WebDAV status codes in TC 3.2.
> I had to change two property files, possibly this could be an explanation,
> why the exception is still in TC 321.
Perhaps. I think it shouldn't throw an exception when it doesn't know the
status code in the first place ;-)
That's not good anyway, since it means lots of people will come and report
that problem. I'll add an item about this to the FAQ page, and I'll also
mention it on the Tomcat-Howto page.
Remy
