Felix Meschberger wrote:
> 
> 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
> 
Yes, thanks - that was what I found and meant with indirections :)
Anyway, it works as expected so I reverted the change.

But it seems that the osgi console is in these cases not displaying the
imports correctly: the javax.jcr classes are not listed in the imported
packages list of the jcr api bundle.

Carsten

-- 
Carsten Ziegeler
[EMAIL PROTECTED]

Reply via email to