[
https://issues.apache.org/jira/browse/SLING-8314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16792468#comment-16792468
]
Karl Pauls commented on SLING-8314:
-----------------------------------
[~kwin], as I already said in the dev list discussion. I think the question is
if we want to change our definition of what we support in the first place. If
we stick with what we currently have defined, we only have to make sure the
writeback ends up writing only capital letter arrays - no?
If we want to change it, then I guess we have to come-up with a proposal of
what to support and how we convert. I still think it wouldn't be optimal to
say: if you give a config via the jcr and then touch it via the webconsole, the
types will changes but I guess we could just do that - however, I think we
should make an explicit decision if so.
> JCR Installer writeback - primitive array types get lower case prefix ,
> convert primitive arrays to Object arrays
> --------------------------------------------------------------------------------------------------------------------
>
> Key: SLING-8314
> URL: https://issues.apache.org/jira/browse/SLING-8314
> Project: Sling
> Issue Type: Bug
> Components: Installer
> Affects Versions: JCR Installer 3.1.26
> Reporter: Ashok Kumar
> Priority: Major
>
> When we put a upper case prefix in our config in the repo and then change it
> via the webconsole it gets the prefix converted into a lower case. This
> creates issues as Sling only support uppercase prefixes.
> As the writeback just uses some class from Felix to write the file back (that
> will write a lower case for primitive arrays and an upper case for Object
> arrays) the fix should be reasonable straight forward by just massaging the
> configurations before writing them out via that class and turning all
> primitive arrays into their respective Object array in updatehandler.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
