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

["Ilyas Türkben (JIRA)" <ji...@apache.org>]

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

Ilyas Türkben commented on SLING-2477:
--------------------------------------

In Sling, the class org.apache.sling.engine.impl.filter.ServletFilterManager:212(org.apache.sling.engine-2.3.10.jar) expects an Integer in order to set the Filter ranking which makes impossible defining filter rankings via sling:OsgiConfig nodes.

> 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 was sent by Atlassian JIRA
(v6.3.4#6332)