[
https://issues.apache.org/jira/browse/STANBOL-1043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13634919#comment-13634919
]
Rupert Westenthaler commented on STANBOL-1043:
----------------------------------------------
This change might cause some troubles for the initialization of Solr Analyzers.
All OSGI bundles that do provide Solr Analyzers do need to use a bundle
activator that loads Solr Analyzer in the local bundle and registers them as
OSGI services. This is necessary because the SPI like way Solr loads Analyzers
(since version 4) is not working within an OSGI environment.
Currently the commons.solr.core module provides an abstract BundleActivator
that does exactly that. If we want to separate the bundles embedding the Solr
dependencies from the Bundles that do provide Stanbol specific extensions we
would need to
1. move the functionality used for registering Solr Analyzers as OSGI services
to an own bundle
2. create one or more bundles that embed the Lucene/Solr dependencies. This
bundles would have a dependency to (1). I would suggest to have at least two
one for the Lucene dependencies and on other for the Solr dependencies
3. commons.solr.core bundle, but without embedded dependencies
4. all other current commons.solr.** modules with no changes
> Apache SOLR should be bundled separately from the Stanbol-specific classes
> --------------------------------------------------------------------------
>
> Key: STANBOL-1043
> URL: https://issues.apache.org/jira/browse/STANBOL-1043
> Project: Stanbol
> Issue Type: Improvement
> Reporter: Sebastian Schaffert
>
> The current bundles for SOLR merge the SOLR and Lucene libraries in bundles
> together with Stanbol specific classes. This should be avoided because it
> makes it impossible to provide SOLR and Lucene from the framework bundle, and
> creates also classloader problems in case Stanbol is run inside a web
> container that already has SOLR running.
--
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
