The static parse method is simply for convenience.... it does nothing that you couldn't do by instantiating an instance of QueryParser and calling the instance 'parse' method. In fact, its more flexible to use QueryParser as an instance than through the static method.

So, you already have what you're requesting with QueryParser.

What exactly are you unit testing and how? I have a feeling if you give us more details of what you're trying to accomplish we could help.

Erik


On Sunday, October 5, 2003, at 05:13 AM, Mike Hogan wrote:


QueryParser.parse also makes it hard for me to unit test.  Would it be
possible to make this a non-static method?

Thanks again,
Mike.

----- Original Message -----
From: "Mike Hogan" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, October 05, 2003 11:09 AM
Subject: [subscriptions] Please make org.apache.lucene.index.IndexWriter
non-final



Hi,

Please can you make org.apache.lucene.index.IndexWriter non-final. It's
being final makes it impossible for me to test using mock objects. Also,
if
there are other public final classes that are significant to the Lucene
API,
please make them non-final also, for the same reason.

One more thing, I see that there are cvs commits on the Lucene project,
but
no releases in a long while. What is the status with repect to new
releases? (In other words, if you do go ahead and make these classes
non-final, when can I expect to be able to make use of the changes :)).


Thanks,
Mike.


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to