[JCR-2536] spi2davex: InvalidItemStateException not properly extracted from ambiguous response error

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0
• Fix Version/s: 2.1
• Component/s: jackrabbit-spi2dav
• Assignee: Angela Schreiber
• Reporter: Angela Schreiber
• Created: 03/Mar/10 18:43
• Updated: 27/Apr/10 08:23
• Resolved: 11/Mar/10 19:14

Description

NodeTest#testSaveInvalidStateException
SessionTest#testSaveInvalidStateException

fail with PathNotFoundException instead of InvalidItemStateException.

i remember that i already addressed that issue in spi2dav a long time ago. with the batched writing in
spi2davex it is back: the server isn't aware of the distinction and just isn't able to retrieve that removed
item... either the client side finds a way to distinguish between path-not-found and externally modified
or we have to leave this as known issue...

in spi2dav i added add quick hack: if the operation was some write operation the path-not-found is
simply converted into invaliditemstateexception.