jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-363) Node.setProperty(String, ...) implementation not according to the specification
Date Mon, 20 Mar 2006 14:40:01 GMT
    [ http://issues.apache.org/jira/browse/JCR-363?page=comments#action_12371087 ] 

Jukka Zitting commented on JCR-363:
-----------------------------------

OK, thanks. I'll merge it in 1.0 on the basis of JSR 170 compliancy. If it does cause a problem,
then we can always release a fix in 1.0.1. I'd rather err with a bug in 1.0 than an API compliancy
issue, especially as the change seems to work just fine for me as well.


> Node.setProperty(String, ...) implementation not according to the specification
> -------------------------------------------------------------------------------
>
>          Key: JCR-363
>          URL: http://issues.apache.org/jira/browse/JCR-363
>      Project: Jackrabbit
>         Type: Bug
>   Components: API
>     Versions: 0.9
>  Environment: svn r387181
>     Reporter: Stefan Guggisberg
>     Assignee: Stefan Guggisberg
>      Fix For: 1.0

>
> to illustrate the issue assume the following  property definition:
> name: someText
> type: String
> non-mandatory
> non-autocreate
> the following call would throw a ConstraintViolationException
> if the property doesn't exist yet:
> node.setProperty("someText", 12345);
> the rules used to find an applicable definition in this case are too strict.

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