You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2008/09/24 09:59:44 UTC
[jira] Resolved: (JCR-664) Property.setValue(Node) explicitly
checks for NodeImpl
[ https://issues.apache.org/jira/browse/JCR-664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcel Reutegger resolved JCR-664.
----------------------------------
Resolution: Won't Fix
+1, see also my previous comment.
> Property.setValue(Node) explicitly checks for NodeImpl
> ------------------------------------------------------
>
> Key: JCR-664
> URL: https://issues.apache.org/jira/browse/JCR-664
> Project: Jackrabbit
> Issue Type: Wish
> Components: jackrabbit-core
> Environment: that's neither a bug nor is it a major issue
> Reporter: Tobias Bocanegra
> Priority: Minor
>
> The implementation of Propert.setValue(Node) explicitly checks if the argument is a NodeImpl:
> if (target instanceof NodeImpl) {
> [...]
> } else {
> String msg = "incompatible Node object: " + target;
> log.debug(msg);
> throw new RepositoryException(msg);
> }
> This is not very convenient for applications that decorate the jcr objects.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.