jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matias Mirabelli (JIRA)" <j...@apache.org>
Subject [jira] Created: (OCM-38) OCM enhanced exceptions.
Date Wed, 28 Oct 2009 20:20:59 GMT
OCM enhanced exceptions.
------------------------

                 Key: OCM-38
                 URL: https://issues.apache.org/jira/browse/OCM-38
             Project: Jackrabbit OCM
          Issue Type: Improvement
         Environment: All operating systems, JDK 1.4+
            Reporter: Matias Mirabelli


We're working with JackRabbit OCM and we need to trap specific exceptions depending on the
context in which occurs, and the OCM just
throws three kind of exceptions: ObjectContentManagerException, RepositoryException and JcrSystemException.

We need to catch exceptions such as PathNotFoundException or PathAlreadyExistsException, since
commonly we use several operations inside the same try block, for example:

try {
    jcrTemplate.remove("/my/repo/path");
    jcrTemplate.save();
} catch (ObjectContentManagerException ex) {
    // Here's the question.
}

In several cases, this is ambiguous and is not possible to know what exception was thrown
without parsing the exception message. We made a patch to the ObjectContentManager implementation
in order to add several useful runtime exceptions, keeping backward compatibility with the
old exceptions.

I'd like to submit a patch for this improvement. Is there a way to attach the patch, or just
can be included as part of the report?

Thank you in advance.

Matias.

-- 
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