jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julian Reschke (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (JCR-1056) JCR2SPI: improve ItemDefinitionProviderImpl.getMatchingPropdef to better handle multiple residuals
Date Wed, 08 Aug 2007 15:14:59 GMT

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

Julian Reschke reassigned JCR-1056:
-----------------------------------

    Assignee: Julian Reschke

> JCR2SPI: improve ItemDefinitionProviderImpl.getMatchingPropdef to better handle multiple
residuals
> --------------------------------------------------------------------------------------------------
>
>                 Key: JCR-1056
>                 URL: https://issues.apache.org/jira/browse/JCR-1056
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: SPI
>            Reporter: Julian Reschke
>            Assignee: Julian Reschke
>            Priority: Minor
>
> When a new property is set with unknown type (missing PropertyType parameter), ItemDefinitionProviderImpl.getMatchingPropdef()
is used to find an applicable property definition.
> There may be cases where multiple residual property defs may match, for instance, when
the repository allows only a certain set of property types on that node type.
> In this case, when the set of allowable types includes STRING, that propdef should be
returned. After all, the client did not specify the type, so STRING is most likely the best
match.

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


Mime
View raw message