You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fx-dev@ws.apache.org by "Aliaksandr Birukou (JIRA)" <ji...@apache.org> on 2006/06/16 16:22:30 UTC

[jira] Created: (ADDR-34) QueryParser is not applicable for the arguments (String, String, Analyzer) in results.jsp when executing search in the browser (demo from Lucene 2.0)

QueryParser is not applicable for the arguments (String, String, Analyzer) in results.jsp when executing search in the browser  (demo from Lucene 2.0)
------------------------------------------------------------------------------------------------------------------------------------------------------

         Key: ADDR-34
         URL: http://issues.apache.org/jira/browse/ADDR-34
     Project: Addressing
        Type: Bug

 Environment: Windows XP
Tomcat 5.5

    Reporter: Aliaksandr Birukou


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: addressing-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: addressing-dev-help@ws.apache.org


[jira] Commented: (ADDR-34) QueryParser is not applicable for the arguments (String, String, Analyzer) in results.jsp when executing search in the browser (demo from Lucene 2.0)

Posted by "Alexander Frink (JIRA)" <ji...@apache.org>.
    [ http://issues.apache.org/jira/browse/ADDR-34?page=comments#action_12460925 ] 
            
Alexander Frink commented on ADDR-34:
-------------------------------------

Since I found the same problem, here is how to fix it:

In results.jsp, replace
                        query = QueryParser.parse(queryString, "contents", analyzer); //parse the
by
                        query = new QueryParser("contents",analyzer).parse(queryString); //parse the

Even with this fix, the search results cannot be clicked, because the have a wrong a href link (null). This can be changed several lines below by replacing
                        String url = doc.get("url");                   //get its url field
with
                        String url = doc.get("path");                   //get its url field



> QueryParser is not applicable for the arguments (String, String, Analyzer) in results.jsp when executing search in the browser  (demo from Lucene 2.0)
> ------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ADDR-34
>                 URL: http://issues.apache.org/jira/browse/ADDR-34
>             Project: Addressing
>          Issue Type: Bug
>         Environment: Windows XP
> Tomcat 5.5
>            Reporter: Aliaksandr Birukou
>
> 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: addressing-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: addressing-dev-help@ws.apache.org


[jira] Commented: (ADDR-34) QueryParser is not applicable for the arguments (String, String, Analyzer) in results.jsp when executing search in the browser (demo from Lucene 2.0)

Posted by "Alexander Frink (JIRA)" <ji...@apache.org>.
    [ http://issues.apache.org/jira/browse/ADDR-34?page=comments#action_12460925 ] 
            
Alexander Frink commented on ADDR-34:
-------------------------------------

Since I found the same problem, here is how to fix it:

In results.jsp, replace
                        query = QueryParser.parse(queryString, "contents", analyzer); //parse the
by
                        query = new QueryParser("contents",analyzer).parse(queryString); //parse the

Even with this fix, the search results cannot be clicked, because the have a wrong a href link (null). This can be changed several lines below by replacing
                        String url = doc.get("url");                   //get its url field
with
                        String url = doc.get("path");                   //get its url field



> QueryParser is not applicable for the arguments (String, String, Analyzer) in results.jsp when executing search in the browser  (demo from Lucene 2.0)
> ------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ADDR-34
>                 URL: http://issues.apache.org/jira/browse/ADDR-34
>             Project: Addressing
>          Issue Type: Bug
>         Environment: Windows XP
> Tomcat 5.5
>            Reporter: Aliaksandr Birukou
>
> 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: addressing-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: addressing-dev-help@ws.apache.org