[
https://issues.apache.org/jira/browse/OAK-3022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14605710#comment-14605710
]
Francesco Mari commented on OAK-3022:
-------------------------------------
[~chetanm], [~reschke], [~mreutegg], {{DocumentNodeStoreService}} reads values
from the framework properties first, and from the component properties next.
The fix for OAK-2962, instead, implements the opposite solution because of how
{{SegmentNodeStoreService}} works.
As asked on [oak-dev|http://markmail.org/message/5slapuge34tjdckx], do we have
to maintain the current behaviour of the component? Can we make
{{SegmentNodeStoreService}} and {{DocumentNodeStoreService}} work the same?
> DocumentNodeStoreService fails to handle empty strings in the OSGi
> configuration
> --------------------------------------------------------------------------------
>
> Key: OAK-3022
> URL: https://issues.apache.org/jira/browse/OAK-3022
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core
> Reporter: Francesco Mari
> Assignee: Francesco Mari
>
> 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 {{DocumentNodeStoreService#prop}},
> it is returned to its caller as a valid configuration value. The callers of
> {{DocumentNodeStoreService#prop}}, instead, expect {{null}} when such an
> empty value is found.
> The method {{DocumentNodeStoreService#prop}} 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)
