Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Date: Sun, 11 Sep 2011 09:29:08 +0000 (UTC)
From: "Jukka Zitting (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Message-ID: 
 <2124975178.14586.1315733348783.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <681879298.32326.1308809027529.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Resolved] (JCR-3003) Tika configuration may use wrong class
 loader
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/JCR-3003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jukka Zitting resolved JCR-3003.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 2.3.0

Fixed in revision 1167687.

> Tika configuration may use wrong class loader
> ---------------------------------------------
>
>                 Key: JCR-3003
>                 URL: https://issues.apache.org/jira/browse/JCR-3003
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: indexing, jackrabbit-core
>            Reporter: Jukka Zitting
>            Assignee: Jukka Zitting
>             Fix For: 2.3.0
>
>
> The configurable Tika parser construction mechanism added in JCR-2864 constructs the parser instance lazily when the first indexing request is made. This may confuse things as the context class loader used by Tika to load all the available parser classes may not always be the class loader used to create the repository. To avoid this problem the Tika parser should be constructed already during normal repository initialization.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira