You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "angela (JIRA)" <ji...@apache.org> on 2009/02/04 18:31:59 UTC

[jira] Assigned: (JCR-1964) VirtualNodeTypeStateProvider creates PropertyState with type != value(s).getType

     [ https://issues.apache.org/jira/browse/JCR-1964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

angela reassigned JCR-1964:
---------------------------

    Assignee: angela

if nobody objects i will commit the proposed fix within the next couple of days.

> VirtualNodeTypeStateProvider creates PropertyState with type != value(s).getType
> --------------------------------------------------------------------------------
>
>                 Key: JCR-1964
>                 URL: https://issues.apache.org/jira/browse/JCR-1964
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-core
>            Reporter: angela
>            Assignee: angela
>         Attachments: JCR-1964.diff
>
>
> VirtualNodeTypeStateProvider creates the item states for the in content representation of the node type definitions and in case of jcr:defaultValues hard codes the type of the property state (thus the jcr property) to PropertyType.STRING.
> the nt-definition of nt:propertyDefinition however states that jcr:defaultValues doesn't have a required type, thus the type should rather be determined based on the values themselves.
> the current behaviour leads situations where
> Property.getType != Property.getValues()[0].getType()
> which from my point of view is a bug.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.