[
https://issues.apache.org/jira/browse/STANBOL-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13619592#comment-13619592
]
Tommaso Teofili commented on STANBOL-1012:
------------------------------------------
It looks good to me, thanks Rupert :)
Regarding ZK support I think we should try to pursue that since many Solr4
installations may need that because of SolrCloud architectures.
> Register Solr AnlyzerFactories as OSGI services and provide OSGI enabled
> SolrResourceLoader
> -------------------------------------------------------------------------------------------
>
> Key: STANBOL-1012
> URL: https://issues.apache.org/jira/browse/STANBOL-1012
> Project: Stanbol
> Issue Type: Sub-task
> Components: Commons
> Reporter: Rupert Westenthaler
> Assignee: Rupert Westenthaler
>
> Starting with Solr 4 an SPI like mechanism is used to locate Analyzers
> Factories. This means that "META-INF/services" are used to locate
> CharFilterFactory, TokenizerFactory and TokenFilterFactory instances.
> This prevents the separation of optional Analyzers in their own modules, as
> "META-INF/services" files can only be loaded from the current bundle (the
> o.a.stanbol.commons.solr.core module).
> To keep the possibility to provide own modules for optional Analyzer
> Factories it is necessary to replace the SPI infrastructure with one that is
> compatible to OSGI. This would mean to
> * write an BundleActivator for all solr modules that searches for according
> "META-INF/services" and registers them with the OSGI service factory.
> * replace the default ServiceLoader with an OSGI on that uses the
> ServiceFactory instead of SPI to find CharFilterFactory, TokenizerFactory or
> TokenFilterFactory instances based on the values configured in the schema.xml.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
