lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steven Parkes (JIRA)" <j...@apache.org>
Subject [jira] Commented: (LUCENE-679) CLONE -QueryParser is not applicable for the arguments (String, String, Analyzer) error in results.jsp when executing search in the browser (demo from Lucene 2.0)
Date Wed, 18 Oct 2006 19:49:36 GMT
    [ http://issues.apache.org/jira/browse/LUCENE-679?page=comments#action_12443344 ] 
            
Steven Parkes commented on LUCENE-679:
--------------------------------------

Hmmm ... I've been wondering about this. Turns out that both the svn tag lucene_2_0_0 and
the 2.0.0 src tar ball have "2.0.1-dev" in common-build.xml. I don't know if this was intentional,
so that the someone using the signed binary tar ball would be clearly distinguishable from
something that someone had built? Wouldint think so, but I'm not too up on ASF release procedures.

In any case, it's easier to understand that someone will see 2.0.1-dev even if they haven't
been working with the lucene_2_0 branch (where I would expect it).

That said, what do we do with issues like this? Close as a dup/already fixed with a release
2.1 and let them lobby for a release if they find it critical?

> CLONE -QueryParser is not applicable for the arguments (String, String, Analyzer) error
in results.jsp when executing search in the browser (demo from Lucene 2.0)
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: LUCENE-679
>                 URL: http://issues.apache.org/jira/browse/LUCENE-679
>             Project: Lucene - Java
>          Issue Type: Bug
>    Affects Versions: 2.0.0
>         Environment: Windows XP
> Tomcat 5.5 
>            Reporter: Ted Cahall
>             Fix For: 2.0.1
>
>
> When executing search in the browser (as described in demo3.html Lucene demo) I get error,
because the demo uses the method (QueryParser with three arguments) which is deleted (it was
deprecated).
> I checked the demo from Lucene 1.4-final it with Lucene 1.4-final - it works, because
those time the method was there.
> But demo from Lucene 2.0 does not work with Lucene 2.0
> The error stack is here:
> TTP Status 500 -
> type Exception report
> message
> description The server encountered an internal error () that prevented it from fulfilling
this request.
> exception
> org.apache.jasper.JasperException: Unable to compile class for JSP
> An error occurred at line: 60 in the jsp file: /results.jsp
> Generated servlet error:
> The method parse(String) in the type QueryParser is not applicable for the arguments
(String, String, Analyzer)
> org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:510)
> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:375)
> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
> org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> root cause
> org.apache.jasper.JasperException: Unable to compile class for JSP
> An error occurred at line: 60 in the jsp file: /results.jsp
> Generated servlet error:
> The method parse(String) in the type QueryParser is not applicable for the arguments
(String, String, Analyzer)
> org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:84)
> org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:328)
> org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java:409)
> org.apache.jasper.compiler.Compiler.compile(Compiler.java:297)
> org.apache.jasper.compiler.Compiler.compile(Compiler.java:276)
> org.apache.jasper.compiler.Compiler.compile(Compiler.java:264)
> org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:563)
> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:303)
> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
> org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> note The full stack trace of the root cause is available in the Apache Tomcat/5.5.15
logs.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org


Mime
View raw message