On Tue, 2006-05-23 at 18:45 +0200, karl wettin wrote:
> On Tue, 2006-05-23 at 10:50 -0500, James Maes wrote:
>
> > It seems to be related to Strings and when they are created.
>
> the bug where the per instance float for maximum score (accuracy) is
> modified instead of using it local in the met
On Tue, 2006-05-23 at 10:50 -0500, James Maes wrote:
> It seems to be related to Strings and when they are created.
Try to create a new instance of SpellChecker for each suggestion. Will
it work? Then you have hit the bug where the per instance float for
maximum score (accuracy) is modified ins
Here is the problem:
We have implemented the lucene eninge within our application server which is
built ontop of Tomcat. We've had no problems creating the indexes or
searching them. The problems we are having are all related to the
SpellChecker part of the system.
It seems to be related to St
