You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2012/04/27 17:16:52 UTC

[jira] [Resolved] (SLING-2450) JcrInstaller generates incorrect node name in /apps/system/config (or else the installer doesn't process the nodename properly)

     [ https://issues.apache.org/jira/browse/SLING-2450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler resolved SLING-2450.
-------------------------------------

    Resolution: Fixed

Hi Tyson,

I'm closing this bug for two reasons:
- the problem you describe is not the same than this issue; it's about reading configurations not writing them back
- I did a quick test and adding config files to the repo, editing them etc. works for me

If you think there still is an issue, please create a new issue with a description how to reproduce the problem. Thanks
                
> JcrInstaller generates incorrect node name in /apps/system/config (or else the installer doesn't process the nodename properly)
> -------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SLING-2450
>                 URL: https://issues.apache.org/jira/browse/SLING-2450
>             Project: Sling
>          Issue Type: Bug
>          Components: Installer
>    Affects Versions: Installer Core 3.3.4, JCR Installer 3.1.2, Installer Configuration Factory 1.0.4
>            Reporter: Tyson Norris
>            Assignee: Carsten Ziegeler
>             Fix For: Installer Core 3.3.6, JCR Installer 3.1.4, Installer Configuration Factory 1.0.6
>
>
> when using ConfigurationAdmin or osgi web console to create a config for a ManagedServiceFactory, a nt:file node is created in /apps/system/config with a node name like:
> com.adobe.granite.auth.oauth.provider.com.adobe.granite.auth.oauth.provider.99bd39e3-4367-47b0-a5a2-b4e1a0f8a5b9.config
> The installer, however will not process the node (and create the managed service propertly) unless the node name is formatted like:
> com.adobe.granite.auth.oauth.provider-99bd39e3-4367-47b0-a5a2-b4e1a0f8a5b9.config
> Note that:
> - "com.adobe.granite.auth.oauth.provider" string only occurs once
> - there is a dash "-" after "provider"
> I'm not sure which problem it is, but it may be one of:
> - the JcrInstaller generates the wrong node name
> - OR the JcrInstaller does not process the node name properly

--
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