Torgeir Veimo wrote:
Marcel Reutegger wrote:
Torgeir Veimo wrote:
Inspection using Luke sounds like a good option. However, it turned
out to be a spelling error being introduced in the text filter
classes "MsreplaceTextFilter", so an exception was being thrown that
disabled text indexing..
hmm, do you mean text filtering was disabled completely? This is not
the intended behaviour. Jackrabbit should only issue a warning message
for the misspelled text filter and proceed initializing the next one.
Can you confirm that none of the text filters were initialized?
Here's the exception:
00:05:04,028 WARN SearchIndex - Invalid TextFilter class:
org.apache.jackrabbit.core.query.MsreplaceTextFilter
java.lang.ClassNotFoundException:
org.apache.jackrabbit.core.query.MsreplaceTextFilter
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1352)
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1198)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:164)
at
org.apache.jackrabbit.core.query.lucene.SearchIndex.setTextFilterClasses(SearchIndex.java:739)
This is what I expected. Jackrabbit issues a warn message, but will
continue with the initialization of the remaining text filters.
regards
marcel
