[ https://issues.apache.org/jira/browse/SLING-2477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13615788#comment-13615788 ]
Ian Boston commented on SLING-2477: ----------------------------------- +1. I'll try and support both formats as they are not mutually exclusive. Its more work, but less than trying to reach consensus. > 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