You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Konrad Windszus (JIRA)" <ji...@apache.org> on 2014/11/18 15:15:34 UTC
[jira] [Created] (SLING-4183) Jcr Installer Provider only supports
storing array values for OSGi Component Properties but not java.util.Vector
Konrad Windszus created SLING-4183:
--------------------------------------
Summary: 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)