You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Tyson Norris (JIRA)" <ji...@apache.org> on 2012/04/26 00:16:18 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13262186#comment-13262186 ]
Tyson Norris commented on SLING-2450:
-------------------------------------
I built snapshot versions:
-rw-r--r-- 1 tnorris admin 130504 Apr 25 13:55 org.apache.sling.installer.core-3.3.5-SNAPSHOT.jar
-rw-r--r-- 1 tnorris admin 24185 Apr 25 13:57 org.apache.sling.installer.factory.configuration-1.0.5-SNAPSHOT.jar
-rw-r--r-- 1 tnorris admin 54277 Apr 25 13:56 org.apache.sling.installer.provider.jcr-3.1.3-SNAPSHOT.jar
But don't see any change.
Adding a node at /apps/system/config/com.adobe.granite.auth.oauth.provider.com.adobe.granite.auth.oauth.provider.514f1954-94c8-48b1-bc65-f96c794a37ce.config should produce a config for provider com.adobe.granite.auth.oauth.provider right?
Thanks
Tyson
> 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