[
https://issues.apache.org/jira/browse/FELIX-6009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16731799#comment-16731799
]
Carsten Ziegeler commented on FELIX-6009:
-----------------------------------------
I'm a little bit lost at the moment as:
ADTest#testDefaultValuesForSingleValuedAttributes checks the current behaviour
with this additional comment:
// corner case: in case of required values, an empty default makes no
sense
// for single values, hence that the empty default is coerced into
null...
> Metatype AD empty String default value
> --------------------------------------
>
> Key: FELIX-6009
> URL: https://issues.apache.org/jira/browse/FELIX-6009
> Project: Felix
> Issue Type: Bug
> Components: Metatype Service
> Affects Versions: metatype-1.2.2
> Reporter: Andreas Lemmer
> Priority: Critical
> Fix For: metatype-1.2.4
>
>
> I have an AD with a default value which is an empty string, like
> {{<AD id="server" type="String" default=""/>}}
> According to the OSGi Spec, the method AttributeDefinition.defaultValue() in
> this case must return an array with one element (which should be the empty
> string), because the cardinality is 0 (implicit) and the default is defined.
> However, the Felix Metatype Service implementation returns null for
> defaultValue().
> In my use case, this breaks everything, because a null value indicates a
> configuration error (default not given, although mandatory) whereas an empty
> string is perfectly fine.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
