You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2008/01/15 09:31:35 UTC
[jira] Resolved: (SLING-155) Jackrabbit-Server and -Client bundles
check Configuration Admin on startup only
[ https://issues.apache.org/jira/browse/SLING-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger resolved SLING-155.
-------------------------------------
Resolution: Fixed
Implement the ServiceListener for jackrabbit-client and -server bundles in Rev. 612037.
Bertrand, can you please verify and close the issue if it works ? Thanks.
> Jackrabbit-Server and -Client bundles check Configuration Admin on startup only
> -------------------------------------------------------------------------------
>
> Key: SLING-155
> URL: https://issues.apache.org/jira/browse/SLING-155
> Project: Sling
> Issue Type: Bug
> Components: Repository
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: 2.0.0
>
>
> The jcr/jackrabbit-server and jcr/jackrabbit-client bundles in the bundle activator verify that at least on configuration is available for the service from the Configuration Admin service. If the Configuration Admin service is not started yet, this check fails, and the verification may only be done by manually restarting the bundle.
> The fix is to register a service listener for the Configuration Admin service in case the service is not available at bundle start time. This listener would verify the configuration as soon as the Configuration Admin service is registered.
> For reference see also [1] and [2]
> [1] http://markmail.org/message/bjryqdn3u2wfxdmf
> [2] http://svn.apache.org/viewvc/incubator/sling/trunk/usling/usling-webapp/README.txt?view=markup
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.