Hi Carsten, Am Donnerstag, den 03.01.2008, 13:42 +0100 schrieb Carsten Ziegeler: > Carsten Ziegeler wrote: > > Felix Meschberger wrote: > >> Not quite: The launcher should be configured such that the Jackrabbit > >> API classes are added to the bootclass path just like the JCR API > >> classes. You still need the jcr/api bundle because it also has the > >> session pooling. > > Yes, right. > > > >> Thanks you OSGi package resolution, the JCR API and Jackrabbit API > >> classes will be used from the system bundle and not from the jcr/api > >> bundle - this is why bundles exporting packages must also import these > >> packages. > >> > > Yepp - is the jcr api currently already added to the boot classpath? > > > Ok, the answer is yes - I got a little bit lost in the indirection of > "sling.include.*" with the property file :) > > So I'll try if putting the jackrabbit api into the boot classpath will > solve the problem and then revert the change.
As long as the Jackrabbit API jar file is in the class path, the Sling Web App (launcher/webapp) is configured to include the jackrabbit API in the boot class path. See http://svn.apache.org/repos/asf/incubator/sling/trunk/launcher/webapp/src/main/webapp/WEB-INF/jcr-client.properties Regards Felix > > Carsten >
