Uploaded image for project: 'Jackrabbit Oak'
  1. Jackrabbit Oak
  2. OAK-3621

Required property type not respected

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments


    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 1.3.12, 1.4
    • core, jcr
    • None


      It seems like Section 7.1.5 Adding and Writing Properties of jsr 170

      						Sets the specified (single value) property of this node
      to the specified value. If the property does not yet
      exist, it is created. The property type of the property
      will be that specified by the node type of this node.
      						If the property type of the supplied Value object is
      different from that required, then a best-effort
      conversion is attempted. If the conversion fails, a
      ValueFormatException is thrown. If another error
      occurs, a RepositoryException is thrown.
      						If the node type of this node does not indicate a
      specific property type, then the property type of the
      supplied Value object is used and if the property
      already exists (has previously been set) it assumes
      both the new value and new property type.

      is not respected.In the provided screenshots you can see a mixin definition having a long property. But the property type in the creation node is Boolean


        1. mixin_definition.png
          140 kB
          Antonio Sanso
        2. OAK-3621_2.patch
          11 kB
          Angela Schreiber
        3. property_type.png
          388 kB
          Antonio Sanso
        There are no Sub-Tasks for this issue.


          This comment will be Viewable by All Users Viewable by All Users


            angela Angela Schreiber
            asanso Antonio Sanso
            0 Vote for this issue
            1 Start watching this issue



              Issue deployment