Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Received-SPF: pass (athena.apache.org: domain of fmeschbe@gmail.com designates
 74.125.78.24 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject
         :content-type:content-transfer-encoding;
        b=fRTNCdjypGm2zf8Q2VgRxMdUxI+O3C4SbsnZPbKr8FWOBzX/Afw2HQnqozq3fTZAaf
         VMS/bMH1Uoyxf5k0OGun12DoSHMJ4bhkeu13c81ChD5nQBO0U7PkbfQcovb4ynp5wbu1
         DTdiBj5mC+eA/LlTPh9fckZhA+HjVroVd/+jM=
Message-ID: <48D778E4.3070203@gmail.com>
Date: Mon, 22 Sep 2008 12:52:20 +0200
From: Felix Meschberger <fmeschbe@gmail.com>
User-Agent: Thunderbird 2.0.0.14 (X11/20080501)
MIME-Version: 1.0
To: Jackrabbit Dev <dev@jackrabbit.apache.org>
Subject: Release 1.4.1 of Jackrabbit ClassLoader
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 7bit

Hi all,

I just fixed a nasty bug in the Jackrabbit ClassLoader [1], which
exhibits problems when trying to use the classloader on files created
with Jackrabbit WebDAV. The problem is that the Jackrabbit ClassLoader
assumes the files to be nt:file nodes whose jcr:content child node is of
type nt:resource. The Jackrabbit Simple WebDAV implementation on the
other hand creates the jcr:content child nodes as nt:unstructured nodes
by default.

This causes the Jackrabbit ClassLoader to fail access.

Because this issue affects the functionality of the JSP compiler of the
Apache Sling project, I propose to cut a release (1.4.1) of the
Jackrabbit ClassLoader module in the next days, so that the Sling JSP
Compiler can work smoothly together with files created through
Jackrabbit Simple WebDAV.

WDYT ?

Regards
Felix


[1] https://issues.apache.org/jira/browse/JCR-1749