SlingServerRepository does not start in launchpad/webapp or launchpad/testing
-----------------------------------------------------------------------------

                 Key: SLING-1177
                 URL: https://issues.apache.org/jira/browse/SLING-1177
             Project: Sling
          Issue Type: Bug
          Components: Launchpad
            Reporter: Bertrand Delacretaz


As reported by Peter Chiochetti [1], the SlingServerRepository does not start 
in launchpad/webapp or launchpad/testing in the current trunk.

The factory service seems to be created correctly, and a configuration is 
listed (like SlingServerRepository.d1ccdeef-93bc-482b-9672-965fce5c7e7a), but 
the service is not present.

In the logs below, "Component Factory cannot be configured by factory 
configuration" seems to indicate a declarative services problem.

launchpad/app starts correctly, not sure what the difference is

[1] 
http://mail-archives.apache.org/mod_mbox/sling-users/200911.mbox/%[email protected]%3e

Log excerpts:
09.11.2009 13:37:02.654 *INFO* [FelixStartLevel] 
org.apache.sling.jcr.jackrabbit.server.impl.Activator verifyConfiguration: 
Created configuration 
org.apache.sling.jcr.jackrabbit.server.SlingServerRepository.b8fd82e6-bdb9-41f9-9b2f-43cc4f6d155c
 for org.apache.sling.jcr.jackrabbit.server.SlingServerRepository
09.11.2009 13:37:02.700 *ERROR* [FelixStartLevel] 
org.apache.sling.jcr.jackrabbit.server 
[org.apache.sling.jcr.jackrabbit.server.SlingServerRepository] Component 
Factory cannot be configured by factory configuration
09.11.2009 13:37:02.732 *INFO* [SCR Component Actor] org.apache.felix.scr 
Running task: Enable Component: 
org.apache.sling.jcr.jackrabbit.server.SlingServerRepository (10)
09.11.2009 13:37:02.747 *INFO* [SCR Component Actor] 
org.apache.sling.jcr.jackrabbit.server Service 
[org.apache.sling.jcr.jackrabbit.server.SlingServerRepository,27] ServiceEvent 
REGISTERED


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to