Re: [Exist-open] Setting up a new Lucene tokenizer/analyzer

[Efraim F. <efr...@gm...>]

On 05/08/2011 02:48 PM, Wolfgang Meier wrote:
>> I'm having some issues setting up a custom tokenizer/analyzer in eXist,
>> and I wanted to know if I'm doing anything obviously wrong.
> I can't see anything obviously wrong in the lucene index
> configuration, but the tokenizer setting in conf.xml is for eXist's
> old (now deprecated) full-text index and won't work with the lucene
> tokenizer. Does it help if you reset that to the old setting? I don't
> expect it does.

Unfortunately, I spoke too soon on this one. When I reinstalled the db, 
I had forgotten to copy the analyzer into the classpath. When it's 
there, I still get the same NPE. I also get an additional error when 
trying to store a file in the database through the admin client: 
"Impossible to store a resource [path]: null"

The resource appears anyway, and there's no exception in the logs.

Thanks,


-- 
---
Efraim Feinstein
Lead Developer
Open Siddur Project
http://opensiddur.net
http://wiki.jewishliturgy.org