[ http://issues.apache.org/jira/browse/JCR-265?page=all ]
Marcel Reutegger closed JCR-265:
--------------------------------
Fix Version: 1.0
Resolution: Fixed
>From now on text filter implementations must be configured in the
>workspace.xml file. Using the service registry does not seem to work stable
>enough with context classloaders.
Sample configuration:
...
<SearchIndex class="org.apache.jackrabbit.core.query.lucene.SearchIndex">
<param name="path" value="${wsp.home}/index" />
<param name="textFilterClasses"
value="org.apache.jackrabbit.core.query.MsExcelTextFilter,org.apache.jackrabbit.core.query.MsPowerPointTextFilter,org.apache.jackrabbit.core.query.MsWordTextFilter,org.apache.jackrabbit.core.query.PdfTextFilter"
/>
</SearchIndex>
...
Fixed in revision: 330282
> Bug with textfilters and classloaders
> -------------------------------------
>
> Key: JCR-265
> URL: http://issues.apache.org/jira/browse/JCR-265
> Project: Jackrabbit
> Type: Bug
> Components: query
> Environment: Eclipse RCP and anyother system that loads libraries within
> several classloaders
> Reporter: Martin Perez
> Fix For: 1.0
>
> I'm having problems with text filter service. I built the contrib/textfilters
> package and I included the resulting jackrabbit-textfilters-1.0-SNAPSHOT.jar
> in my application classpath. The problem is that TextFilterService class is
> unable to find any filters, even though that a
> services/org...TextFilterService file is wihin the META-INF jar's directory.
> I think that this must to be with Eclipse RCP classloader mechanism, but the
> fact is that it does not work. I find a little bit strange this way to load
> services, and as you can see, it seems problematic in some scenarios.
> ----
> Marcel Reutegger
> <[EMAIL PROTECTED]> to jackrabbit-dev
> More options 11:01 am (55 minutes ago)
> Hi Martin,
> we had a similar problem with the query languages, but I solved that one
> by telling the registry to use a specific classloader. this seemed to work.
> I'm not sure this will also work for the text filters, because the jar
> file might be in another classloader.
> could you please post a jira bug? I'll then change the discovery
> mechanism to use good old xml config ;)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
