jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christoph Kiehl (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JCR-808) Better error message for non-trivial nodetype changes
Date Thu, 22 Mar 2007 11:08:32 GMT

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

Christoph Kiehl updated JCR-808:
--------------------------------

    Attachment: patch.txt

This patch is just a proposal. Please review. I didn't use StringBuilder for message construction
on purpose because I think it's more readable this way and performance shouldn't be an issue
here.
I uncommented the code for handling non-trivial changes because it doesn't work right now
anyway. We could uncomment it when checkForConflictingContent() is implemented.

> Better error message for non-trivial nodetype changes
> -----------------------------------------------------
>
>                 Key: JCR-808
>                 URL: https://issues.apache.org/jira/browse/JCR-808
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 1.0, 1.0.1, 1.1, 1.1.1, 1.2.1, 1.2.2, 1.2.3
>            Reporter: Christoph Kiehl
>            Priority: Minor
>         Attachments: patch.txt
>
>
> Currently Jackrabbit only throws a RepositoryException with the message "Not yet implemented".
This says almost nothing to newcomers and is very time consuming to debug even if you know
what is means. It would be better to use the information already availble through NodeTypeDefDiff
to provide a more descriptive error message.

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