jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Mueller" <thomas.tom.muel...@gmail.com>
Subject Re: [jira] Updated: (JCR-664) Property.setValue(Node) explicitly checks for NodeImpl
Date Tue, 05 Dec 2006 15:40:32 GMT
Hi,

Log Wrapper: I didn't know about this problem. It is possible to
unwrap the object in the log wrapper before calling the method.

Thomas


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