Couldn't QueryParser catch the Error and throw an Exception?
"Subclasses of Error, unlike subclasses of Exception, should not be caught
and generally cause termination of the program. Subclasses of Error need not
be declared in the throws clause of a method definition."
I am complaining, because my Servlet just crashed, even though it had a
try{}catch(Exception e){}, which should catch everything, unless catching is
worthless anyways (OutOfMemoryError) :-).
> -----Ursprungliche Nachricht-----
> Von: Halacsy Peter [mailto:[EMAIL PROTECTED]]
> Gesendet: December 7, 2001 3:06 PM
> An: Lucene Users List
> Betreff: Re: AW: Lexical Error
>
>
> Christian Schrader wrote:
>
> >Is there a good reason, why the QueryParser should throw an
> Error instead of
> >an Exception?
> >
> Unfortunatly this is the feature of JavaCC and not only of Lucene's
> QueryParser.
>
> peter
>
> >
> >>-----Ursprungliche Nachricht-----
> >>Von: Christian Schrader [mailto:[EMAIL PROTECTED]]
> >>Gesendet: December 7, 2001 12:57 PM
> >>An: Lucene Users List
> >>Betreff: Lexical Error
> >>
> >>
> >>I just encountered an Error searching for a Term like ${test}.
> >>org.apache.lucene.queryParser.TokenMgrError: Lexical error at
> >>line 1, column
> >>1. Encountered: "$" (36), after : ""
> >>
> >>Is this error known?
> >>
> >>Chris
> >>
> >>
> >>--
> >>To unsubscribe, e-mail:
> >><mailto:[EMAIL PROTECTED]>
> >>For additional commands, e-mail:
> >><mailto:[EMAIL PROTECTED]>
> >>
> >>
> >
> >
> >--
> >To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
>For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
>
--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
