Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <298236681.507191269602067246.JavaMail.jira@brutus.apache.org>
Date: Fri, 26 Mar 2010 11:14:27 +0000 (UTC)
From: "angela (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Created: (JCR-2585) spi2davex: unspecific BadRequest error
 instead of error code matching the RepositoryException
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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: Improvement
          Components: jackrabbit-jcr-server, jackrabbit-spi2dav
    Affects Versions: 2.0.0
            Reporter: angela


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.