[jira] [Commented] (SLING-2477) Configuration via sling:OsgiConfig nodes does not support all types

["Felix Meschberger (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SLING-2477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13274560#comment-13274560 ] 

Felix Meschberger commented on SLING-2477:
------------------------------------------

I support the general idea.

Yet, I suggest we use the same encoding for string values as we do the configuration properties files supported by JCR Install.

Clarification: JCR typing and Configuration Admin typing are overlapping. Neither is a subset of the other.
                
> 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
>
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira