Since the recent set of releases in Sling I am unable to get a system based on Sling to start. We were building a standalone server based on the launchpad bundles, base and app. In general the current snapshot version of those. However since we have a modified server bundle which I haven't upgraded to 1.6 at the moment, I am now building the bundles locally using the 2.1.0 base jar and app.

First off, I get 108 out of 108 bundles active.

http://localhost:8080/ responds with a 503, no repository
I can get to http://localhost:8080/system/console/bundles (108 active bundles) When I go to http://localhost:8080/system/console/components I get 174 components but a lot have unsatisfied dependencies.

All lead back to the SlingRepository

The org.apache.sling.jcr.jackrabbit.server.SlingServerRepository component is fully active and I believe the SlingServerRepository implements a SlingRepository as a Factory.

2 things.
I see the repository pinger  doing

02.12.2009 16:14:56.324 *INFO* [Repository Pinger] org.apache.sling.jcr.jackrabbit.server Using configuration file /Users/ ieb/timefields/open-experiments/slingtests/osgikernel/sling/jackrabbit/ repository.xml 02.12.2009 16:14:56.325 *ERROR* [Repository Pinger] org.apache.sling.jcr.jackrabbit.server startRepository: Uncaught Throwable trying to access Repository, calling stopRepository() (java.lang.NoClassDefFoundError: org/apache/jackrabbit/core/config/ RepositoryConfig) java.lang.NoClassDefFoundError: org/apache/ jackrabbit/core/config/RepositoryConfig at org .apache .sling .jcr .jackrabbit .server .impl .SlingServerRepository.acquireRepository(SlingServerRepository.java:118) at org .apache .sling .jcr .base .AbstractSlingRepository.startRepository(AbstractSlingRepository.java: 805) at org .apache .sling .jcr.base.AbstractSlingRepository.run(AbstractSlingRepository.java:935)
        at java.lang.Thread.run(Thread.java:613)


Any ideas, pointers ?

Is this a classloader thing (I have 3.0.0 of the base jcr classloader and 1.1.0 of the commons classloader)


Thanks
Ian






Reply via email to