[
https://issues.apache.org/jira/browse/JCR-1201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12539650
]
Jukka Zitting commented on JCR-1201:
------------------------------------
This seems like a recipe for complex bootstrapping issues... I see the use
case, but I don't think something like this is architecturally sound.
> Enable to load the indexing configuration from the repository with a config
> path like jcr:/location/in/my/workspace
> -------------------------------------------------------------------------------------------------------------------
>
> Key: JCR-1201
> URL: https://issues.apache.org/jira/browse/JCR-1201
> Project: Jackrabbit
> Issue Type: New Feature
> Components: jackrabbit-core
> Affects Versions: 1.3.3
> Reporter: Ard Schrijvers
> Priority: Minor
> Fix For: 1.4
>
>
> ATM, you can provide an indexing configuration file via <SearchIndex>
> configuration like
> <param name="indexingConfiguration"
> value="path-to-indexing-configuration-file"/>.
> Also see:
> 1) http://wiki.apache.org/jackrabbit/IndexingConfiguration
> 2) http://wiki.apache.org/jackrabbit/Search.
> the 'path-to-indexing-configuration-file' currently must be a file in the
> file system. Support for a indexing configuration which resides in the
> repository itself by enabling some path protocol like
> jcr://location/in/workspace in the configuration. Specifically for war
> deployment configuration files in the repository itself might be very useful.
> Perhaps adding an EventListener for instant re-configuration when the
> indexing configuration changes might be nice as well, though some (most)
> changes in the indexing configuration might require re-indexing, which would
> be bad to start automatically obviously.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
