Created: (JCR-363) Node.setProperty(String, ...) implementation not according to the specification

Node.setProperty(String, ...) implementation not according
to the specification 
------------------------------------------------------------
--------------------

         Key: JCR-363
         URL: http://i
ssues.apache.org/jira/browse/JCR-363
     Project: Jackrabbit
        Type: Bug
  Components: API  
    Versions: 0.9    
 Environment: svn r387181
    Reporter: 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.atl
assian.com/software/jira

    [ http://issues.apache.org/jira/browse/J
CR-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://i
ssues.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.atl
assian.com/software/jira

    [ http://issues.apache.org/jira/browse/J
CR-363?page=comments#action_12371083 ] 

Stefan Guggisberg commented on JCR-363:
---------------------------------------

i targeted 1.0 as this is imo a major bug, causing jsr170
compliancy issues.

i tested the fix and found no problems whatsoever. however
it's a relatively small but non-trivial change. judging the
risk
of unexpected regressions is very difficult.

maybe we should target 1.0.1 instead.

> Node.setProperty(String, ...) implementation not
according to the specification
>
------------------------------------------------------------
-------------------
>
>          Key: JCR-363
>          URL: http://i
ssues.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.atl
assian.com/software/jira

    [ http://issues.apache.org/jira/browse/J
CR-363?page=comments#action_12371081 ] 

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

Should I merge this with 1.0? How high is the chance of
unexpected regressions caused by r387211?

> Node.setProperty(String, ...) implementation not
according to the specification
>
------------------------------------------------------------
-------------------
>
>          Key: JCR-363
>          URL: http://i
ssues.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.atl
assian.com/software/jira

     [ http://issues.apache.org/jira/browse/JCR-363?page=all ]
     
Stefan Guggisberg closed JCR-363:
---------------------------------

    Resolution: Fixed

fixed in svn r387211

> Node.setProperty(String, ...) implementation not
according to the specification
>
------------------------------------------------------------
-------------------
>
>          Key: JCR-363
>          URL: http://i
ssues.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.atl
assian.com/software/jira

     [ http://issues.apache.org/jira/browse/JCR-363?page=all ]

Stefan Guggisberg reassigned JCR-363:
-------------------------------------

    Assign To: Stefan Guggisberg

> Node.setProperty(String, ...) implementation not
according to the specification
>
------------------------------------------------------------
-------------------
>
>          Key: JCR-363
>          URL: http://i
ssues.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.atl
assian.com/software/jira