You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Amit Jain (JIRA)" <ji...@apache.org> on 2015/06/24 06:26:43 UTC
[jira] [Resolved] (OAK-2962) SegmentNodeStoreService fails to
handle empty strings in the OSGi configuration
[ https://issues.apache.org/jira/browse/OAK-2962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amit Jain resolved OAK-2962.
----------------------------
Resolution: Fixed
Committed in trunk with http://svn.apache.org/r1687171
> SegmentNodeStoreService fails to handle empty strings in the OSGi configuration
> -------------------------------------------------------------------------------
>
> Key: OAK-2962
> URL: https://issues.apache.org/jira/browse/OAK-2962
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: segmentmk
> Reporter: Francesco Mari
> Assignee: Amit Jain
> Fix For: 1.3.2
>
> Attachments: OAK-2962-01.patch, OAK-2962-02.patch
>
>
> When an OSGi configuration property is removed from the dictionary associated to a component, the default value assigned to it is an empty string.
> When such an empty string is processed by {{SegmentNodeStoreService#lookup}}, it is returned to its caller as a valid configuration value. The callers of {{SegmentNodeStoreService#lookup}}, instead, expect {{null}} when such an empty value is found.
> The method {{SegmentNodeStoreService#lookup}} should check for empty strings in the OSGi configuration, and treat them as {{null}} values.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)