Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <2049388443.420121266762927891.JavaMail.jira@brutus.apache.org>
Date: Sun, 21 Feb 2010 14:35:27 +0000 (UTC)
From: "fabrizio giustina (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Updated: (JCR-2504) Allow indexingConfiguration to be loaded
 from the classpath
In-Reply-To: <1624529392.420101266762927879.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

fabrizio giustina updated JCR-2504:
-----------------------------------

    Attachment: indexingConfiguration_classpath.diff

SearchIndex patch

> Allow indexingConfiguration to be loaded from the classpath
> -----------------------------------------------------------
>
>                 Key: JCR-2504
>                 URL: https://issues.apache.org/jira/browse/JCR-2504
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: indexing
>    Affects Versions: 1.6.1, 2.0.0
>            Reporter: fabrizio giustina
>         Attachments: indexingConfiguration_classpath.diff
>
>
> The "indexingConfiguration" attribute in the SearchIndex configuration (http://wiki.apache.org/jackrabbit/IndexingConfiguration) actually requires an absolute filesystem path.
> It would be nice if SearchIndex would also accept a file available in the classpath... although you can use variables like ${wsp.home} or similar there are many scenarios where a classpath resource would help (for example when creating a new workspace the directory structure is automatically created by jackrabbit and doesn't need to be already available but the indexing configuration file does).
> I am attaching a simple patch to SearchIndex that tries to load the file from the classpath if it has not been found. Since priority is given to the old behavior (file before classpath) so it's fully backward compatible.
> Diff has been generated against trunk, it would be nice to have this patch also on the 2.0 branch.
>  
>  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.