You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Julian Reschke (JIRA)" <ji...@apache.org> on 2007/08/08 17:14:59 UTC
[jira] Created: (JCR-1056) JCR2SPI: improve
ItemDefinitionProviderImpl.getMatchingPropdef to better handle multiple
residuals
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
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.
[jira] Assigned: (JCR-1056) JCR2SPI: improve
ItemDefinitionProviderImpl.getMatchingPropdef to better handle multiple
residuals
Posted by "Julian Reschke (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Resolved: (JCR-1056) JCR2SPI: improve
ItemDefinitionProviderImpl.getMatchingPropdef to better handle multiple
residuals
Posted by "Julian Reschke (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julian Reschke resolved JCR-1056.
---------------------------------
Resolution: Fixed
Changed as proposed with revision 563916.
> 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.
[jira] Updated: (JCR-1056) JCR2SPI: improve
ItemDefinitionProviderImpl.getMatchingPropdef to better handle multiple
residuals
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting updated JCR-1056:
-------------------------------
Fix Version/s: 1.4
> 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
> Fix For: 1.4
>
>
> 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.