[
https://issues.apache.org/jira/browse/JCR-2536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela resolved JCR-2536.
-------------------------
Resolution: Fixed
Fix Version/s: 2.1.0
Assignee: angela
> spi2davex: InvalidItemStateException not properly extracted from ambiguous
> response error
> -----------------------------------------------------------------------------------------
>
> Key: JCR-2536
> URL: https://issues.apache.org/jira/browse/JCR-2536
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-spi2dav
> Affects Versions: 2.0.0
> Reporter: angela
> Assignee: angela
> Fix For: 2.1.0
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
