lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 20081] New: - Caching problem with JSP:Search tag
Date Tue, 20 May 2003 19:18:52 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20081>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20081

Caching problem with JSP:Search tag

           Summary: Caching problem with JSP:Search tag
           Product: Lucene
           Version: 1.2
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Search
        AssignedTo: lucene-dev@jakarta.apache.org
        ReportedBy: blaplante@netwebapps.com


Hi all,
I have been working on a few issues with the ability to crash the JSP:Search
tag when no criteria have been submitted. With out imposing validation
restrictions on the tag itself I put in some more robust exception handling
and put into place some fail safe logic that will abort the tag if there is
a problem. I added a new attribute called throwOnException="true|false" so
that if you want to do debugging you can turn it on. Each line of lucene
code that throws exceptions looks like this.

try{
    //volatile code here
}catch(SomeException e)
    if(throwOnException){
        throw new JspException("class name: " + e);
    }
    abort = true;
}

if any of the code fails the tag expose the current variable state into the
PAGE_SCOPE and exit. I am having a problem with caching. I am not sure if it
is a problem with Tom Cat or the search engine. I hope you can give me some
advice.

When I run the tag and pass it good criteria the tag responds with the
results as expected. When I hit the back button and submit an empty form
field the tag stops processing as expected but still shows the hitCount from
the previous query, ever there after I can not get the tag to produce
results from an criteria, the values from the previous run are cached. Is
this a Tom Cat setting or am I doing something wrong in the way I am
processing the tag?

I am posting the entire tag at the bottom of this email but if there is a
better way to provide the example please let me know. I will also submit it
as a bug report.

Bryan LaPlante

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


Mime
View raw message