[
https://issues.apache.org/jira/browse/SLING-4183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14216236#comment-14216236
]
Carsten Ziegeler commented on SLING-4183:
-----------------------------------------
Using JCR directly with the config node type has several flaws, the vector is
one of them, missing support of native types like integer or character are
others.
Therefore, we support also the format used by Apache Felix ConfigAdmin - which
is a special properties file that supports all these things including vectors.
So instead of adding all this stuff to nodes, using the properties file is imho
the better/easier solution
> Jcr Installer Provider only supports storing array values for OSGi Component
> Properties but not java.util.Vector
> ----------------------------------------------------------------------------------------------------------------
>
> Key: SLING-4183
> URL: https://issues.apache.org/jira/browse/SLING-4183
> Project: Sling
> Issue Type: Improvement
> Components: Installer
> Affects Versions: JCR Installer 3.1.8
> Reporter: Konrad Windszus
>
> The OSGi Compendium 4.3.0, $105.14.3.13 defines two storage formats for
> multivalue entries: one is vector and the other one is array.
> As long as a configuration is maintained via the Felix Webconsole, it will
> stick to the data format being given in the metatype manifest (through the
> cardinality attribute).
> If the JCR Installer is used to deploy the OSGi configuration it will always
> use array, in case the property is a multivalue property in the JCR
> (https://github.com/apache/sling/blob/trunk/installer/providers/jcr/src/main/java/org/apache/sling/installer/provider/jcr/impl/ConfigNodeConverter.java#L99)
> In the best case the JCR Installer should evaluate the metatype manifest as
> well. Or it should support {{Vector}}s through some special prefix on a
> multivalue property name.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
