Mailing-List: contact sling-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: sling-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of fmeschbe@gmail.com designates
 209.85.134.189 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=subject:from:to:in-reply-to:references:content-type:date:message-id:mime-version:x-mailer:content-transfer-encoding;
        b=ql7P67T44yufbmAkmclSkO0o6z6ubuhj72n/iFk7DuL2xoct0e5Ed9Rj+gHcylWK/zJoE8RQve1qfE5nydsB7MUUQfGdB9Cxd+Hm+LY9jTM3TXRHvoOw61i9IbCjPgE35XbyfMItMWnlK93cvjQgx8RQnY89YgNA8bzcLyVtwfs=
Subject: Re: svn commit: r607215
	-	in	/incubator/sling/trunk/jcr/api/src/main/java/org/apache/sling/jcr/api:
	NodeTypeLoader.java internal/loader/Loader.java
From: Felix Meschberger <fmeschbe@gmail.com>
To: sling-dev@incubator.apache.org
In-Reply-To: <477CD84B.6020001@apache.org>
References: <20071228115150.B01A31A9832@eris.apache.org>
	 <1198867733.4273.15.camel@bslm-046.corp.day.com>
	 <47789959.8020103@apache.org>
	 <1199090113.3979.3.camel@bslm-046.corp.day.com>
	 <4778BC09.4040605@apache.org>
	 <1199103285.3979.14.camel@bslm-046.corp.day.com>
	 <477913A7.9000209@apache.org>
	 <1199185210.3979.20.camel@bslm-046.corp.day.com>
	 <477B48D4.7090101@apache.org>
	 <510143ac0801020200n513b20bdl8ebb6ab891d2fd94@mail.gmail.com>
	 <1199344802.3396.12.camel@bslm-046.corp.day.com>
	 <477CAA6D.6060900@apache.org>
	 <1199353429.8080.17.camel@bslm-046.corp.day.com>
	 <477CD6B7.1080005@apache.org>  <477CD84B.6020001@apache.org>
Content-Type: text/plain
Date: Thu, 03 Jan 2008 13:49:59 +0100
Message-Id: <1199364599.8080.48.camel@bslm-046.corp.day.com>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

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
>