jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tobias Bocanegra (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-664) Property.setValue(Node) explicitly checks for NodeImpl
Date Tue, 05 Dec 2006 15:48:22 GMT
    [ http://issues.apache.org/jira/browse/JCR-664?page=comments#action_12455673 ] 
            
Tobias Bocanegra commented on JCR-664:
--------------------------------------

if the JCR API takes a javax.jcr.Node, then it should work with any implementation. This might
not work for all cases, i agree, but in this case, reading the UUID of the referenceable is
implementation independent.

> Property.setValue(Node) explicitly checks for NodeImpl
> ------------------------------------------------------
>
>                 Key: JCR-664
>                 URL: http://issues.apache.org/jira/browse/JCR-664
>             Project: Jackrabbit
>          Issue Type: Wish
>         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.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message