jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Guggisberg (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-664) Property.setValue(Node) explicitly checks for NodeImpl
Date Wed, 24 Sep 2008 08:21:44 GMT

    [ https://issues.apache.org/jira/browse/JCR-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634062#action_12634062
] 

Stefan Guggisberg commented on JCR-664:
---------------------------------------

+1 for 'Won't Fix'

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


Mime
View raw message