[
https://issues.apache.org/jira/browse/JCR-3014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13064695#comment-13064695
]
Alex Parvulescu commented on JCR-3014:
--------------------------------------
ok, I did a full rollback. this needs more thought.
I didn't really like the fact that in a lot of places the actual error is
wrapped into a repository exception and then thrown again.
so this seemed the easiest way to handle the problem.
your solution is more involved, there will be a lot of changes, but I guess in
the in the end a cleaner api is more beneficial.
also, by 'MalformedIdentifierException' do you mean creating a new exception
class?
> Identifier paths for inexistent items throw exception
> -----------------------------------------------------
>
> Key: JCR-3014
> URL: https://issues.apache.org/jira/browse/JCR-3014
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Reporter: Marcel Reutegger
> Assignee: Alex Parvulescu
> Fix For: 2.3.0
>
>
> The following fails with a RepositoryException but it should rather return
> false:
> session.itemExists("[" + UUID.randomUUID() + "]")
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
