ok, after some re-thinking I will rather create a new contrib and introduce an
spellchecker interface in jackrabbit-core (well, I intended to do that
anyway...). the jackrabbit-spellchecker (?) will then be similar to the
wordnet-synonyms contrib. if you want the spellchecker functionality you need to
configure it and deploy the relevant jar files.
regards
marcel
Marcel Reutegger wrote:
Felix Meschberger wrote:
Why does this extension have to reside in the Jackrabbit core ? If at
all possible, it should also be made an add-on/extension to the core.
This way adding the extension would also require addition of the
dependencies and therefore copying/refactoring is not required.
the spellchecker would be an integral part of the lucene query handler
implementation, which is contained in jackrabbit-core. if the
spellchecker is an optional add-on to the query handler you have to
configure it when you want to use it. that seems overcomplicated and I'd
like to avoid that.
we could of course separate the query handler implementation from the
core but since we only have one implementation I don't see how that is
useful.
Otherwise, you might want to use the maven dependency plugin to copy the
required classes into the destination location at build time.
sounds like an interesting option.
BTW: What is the use of a spellchecker in an infrastructure component
like a JCR repository ?
because that's the only reasonable way to implement spell checking of
fulltext query statements. just using an external dictionary results in
bad suggestions and it is not able to consider content that is actually
present in the repository.
regards
marcel
