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 (Commented) (JIRA)" <ji...@apache.org> on 2012/03/28 20:03:27 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=13240588#comment-13240588 ]
Tyson Norris commented on SLING-2450:
-------------------------------------
In my test, adding a node to /apps/system/config named in the same way as the generated node (e.g. com.adobe.granite.auth.oauth.provider.com.adobe.granite.auth.oauth.provider.955d9a39.10ad9a1b-d610-4c18-a816-4a774dfcb2cf.config) results in this log message, with an incorrect service.factoryPid:
28.03.2012 10:26:24.422 *INFO* [OsgiInstallerImpl] org.apache.sling.audit.osgi.installer Installed configuration com.adobe.granite.auth.oauth.provider.com.adobe.granite.auth.oauth.provider.955d9a39.10ad9a1b-d610-4c18-a816-4a774dfcb2cf from resource TaskResource(url=jcrinstall:/apps/system/config/com.adobe.granite.auth.oauth.provider.com.adobe.granite.auth.oauth.provider.955d9a39-9231-43e8-9d67-11111111.config, entity=config:com.adobe.granite.auth.oauth.provider.com.adobe.granite.auth.oauth.provider.955d9a39.9231-43e8-9d67-11111111, state=INSTALL, attributes=[org.apache.sling.installer.api.tasks.ResourceTransformer=:50:, service.factoryPid=com.adobe.granite.auth.oauth.provider.com.adobe.granite.auth.oauth.provider.955d9a39, service.pid=9231-43e8-9d67-11111111], digest=5abc3a8c9c399d8d9d510641ab388577)
If instead I name a node com.adobe.granite.auth.oauth.provider-955d9a39-9231-43e8-9d67-11111111.config, the correct factoryPid is used and config appears as expected:
28.03.2012 10:44:17.349 *INFO* [OsgiInstallerImpl] org.apache.sling.audit.osgi.installer Installed configuration com.adobe.granite.auth.oauth.provider.618f4315-4a0d-4ede-9657-0e32e0215d83 from resource TaskResource(url=jcrinstall:/apps/system/config/com.adobe.granite.auth.oauth.provider-955d9a39-9231-43e8-9d67-11111111.config, entity=config:com.adobe.granite.auth.oauth.provider.955d9a39-9231-43e8-9d67-11111111, state=INSTALL, attributes=[org.apache.sling.installer.api.tasks.ResourceTransformer=:50:, service.factoryPid=com.adobe.granite.auth.oauth.provider, service.pid=955d9a39-9231-43e8-9d67-11111111], digest=65741728327d3b692b0272c53691a04a)
> 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: JCR Installer 3.1.2
> Reporter: Tyson Norris
>
> 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