[
https://issues.apache.org/jira/browse/SLING-2477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13587127#comment-13587127
]
Carsten Ziegeler commented on SLING-2477:
-----------------------------------------
I disagree :) - it's true that this is not very well documented, but that's
just because it never happened and is an open todo. Supporting the config admin
format is a great feature as this allows to create the configuration somewhere
and simply copy this file into a repository.
I still think that people should not edit OSGi configurations in the
repository, there is zero support wrt to available configuration options, valid
values or their meaning. The web console is a way better tool as this leverages
the metat type information. I understand that people did directly edit inside
the repo because changes through the web console were not persisted. But we
fixed this long time ago.
We can argue here forever, and imho we should go with the solution which calls
for the least trouble and that is the I"" notation. If people are able to add a
hello{int} property, they sure will be able to create a hello property with a
value I"353". Both have an artifical syntax and one might look nicer than the
other, but still you need to know what the correct syntax is, so from a
practical pov there is no difference.
> Configuration via sling:OsgiConfig nodes does not support all types
> -------------------------------------------------------------------
>
> Key: SLING-2477
> URL: https://issues.apache.org/jira/browse/SLING-2477
> Project: Sling
> Issue Type: Bug
> Components: Installer
> Affects Versions: JCR Installer 3.1.2
> Reporter: Alexander Klimetschek
> Assignee: Ian Boston
> Attachments: SLING-2477.patch
>
>
> Most notably, the common "service.ranking" needs to be an Integer, while the
> jcr property mapping only allows for "Long" types at the moment. The problem
> is that JCR has a smaller set of property types than the OSGi config admin
> (JCR: String, Boolean, Long, Double, Decimal; OSGi: String, Boolean, Long,
> Integer, Float, Double, and probably more differences...).
> Similarly to properties files (which do it in the value like
> 'service.ranking=I"-10000"' with I=Integer), there must be a way to
> explicitly specify the type regardless of the JCR type. For example, encoding
> it in the property name like "service.ranking{int}".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
