jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "angela (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (JCR-2585) spi2davex: unspecific BadRequest error instead of error code matching the RepositoryException
Date Wed, 31 Mar 2010 12:56:27 GMT

     [ https://issues.apache.org/jira/browse/JCR-2585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

angela resolved JCR-2585.
-------------------------

    Resolution: Fixed

> spi2davex: unspecific BadRequest error instead of error code matching the RepositoryException
> ---------------------------------------------------------------------------------------------
>
>                 Key: JCR-2585
>                 URL: https://issues.apache.org/jira/browse/JCR-2585
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-jcr-server, jackrabbit-spi2dav
>    Affects Versions: 2.0.0
>            Reporter: angela
>            Assignee: angela
>             Fix For: 2.1.0
>
>         Attachments: JCR-2585.patch
>
>
> the JsonDiffHandler#NodeHandler in the server part of the jcr remoting may only throw
IOException
> if an error occurs. this results in unspecific BadRequest responses even if the problem
source was
> something very specific such as e.g. a locked node.
> after having a first glance at this i think that making DiffException a subclass of IOException
would
> allow to generate much more specific responses codes that even include the original exception
> details.
> i will attach a patch as i didn't had time to carefully test it.  [the conformance tests
passed].

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message