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 (Created) (JIRA)" <ji...@apache.org> on 2012/03/22 14:32:22 UTC

[jira] [Created] (SLING-2444) Support configurations with old pid

Support configurations with old pid
-----------------------------------

                 Key: SLING-2444
                 URL: https://issues.apache.org/jira/browse/SLING-2444
             Project: Sling
          Issue Type: Improvement
          Components: Installer
    Affects Versions: JCR Installer 3.1.2
            Reporter: Carsten Ziegeler
            Assignee: Carsten Ziegeler
             Fix For: JCR Installer 3.1.4


With the rewrite of the jcr installer the PID changed from:
org.apache.sling.jcr.install.impl.JcrInstaller
to
org.apache.sling.installer.provider.jcr.impl.JcrInstaller

We should support potential configurations with the old PID by:
- registering a managed service for the old pid
- if a configuration arrives with the old pid, these values overwrite values from the new PID
- log a warning in such cases

All other mechanisms like trying to merge the configs are bound to fail. As there are only a few users having an own configuration for this service anyway, this is the best possible solution

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

[jira] [Closed] (SLING-2444) Support configurations with old pid

Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SLING-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler closed SLING-2444.
-----------------------------------

    
> Support configurations with old pid
> -----------------------------------
>
>                 Key: SLING-2444
>                 URL: https://issues.apache.org/jira/browse/SLING-2444
>             Project: Sling
>          Issue Type: Improvement
>          Components: Installer
>    Affects Versions: JCR Installer 3.1.2
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: JCR Installer 3.1.4
>
>
> With the rewrite of the jcr installer the PID changed from:
> org.apache.sling.jcr.install.impl.JcrInstaller
> to
> org.apache.sling.installer.provider.jcr.impl.JcrInstaller
> We should support potential configurations with the old PID by:
> - registering a managed service for the old pid
> - if a configuration arrives with the old pid, these values overwrite values from the new PID
> - log a warning in such cases
> All other mechanisms like trying to merge the configs are bound to fail. As there are only a few users having an own configuration for this service anyway, this is the best possible solution

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

[jira] [Resolved] (SLING-2444) Support configurations with old pid

Posted by "Carsten Ziegeler (Resolved) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SLING-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler resolved SLING-2444.
-------------------------------------

    Resolution: Fixed

Fixed in revision 1303844
                
> Support configurations with old pid
> -----------------------------------
>
>                 Key: SLING-2444
>                 URL: https://issues.apache.org/jira/browse/SLING-2444
>             Project: Sling
>          Issue Type: Improvement
>          Components: Installer
>    Affects Versions: JCR Installer 3.1.2
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: JCR Installer 3.1.4
>
>
> With the rewrite of the jcr installer the PID changed from:
> org.apache.sling.jcr.install.impl.JcrInstaller
> to
> org.apache.sling.installer.provider.jcr.impl.JcrInstaller
> We should support potential configurations with the old PID by:
> - registering a managed service for the old pid
> - if a configuration arrives with the old pid, these values overwrite values from the new PID
> - log a warning in such cases
> All other mechanisms like trying to merge the configs are bound to fail. As there are only a few users having an own configuration for this service anyway, this is the best possible solution

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