Bug 7934 - QueryTagSupport will always set maxRows to -1 if not using a context initialization parameter.
Summary: QueryTagSupport will always set maxRows to -1 if not using a context initiali...
Status: RESOLVED FIXED
Alias: None
Product: Taglibs
Classification: Unclassified
Component: Standard Taglib (show other bugs)
Version: unspecified
Hardware: All All
: P3 major (vote)
Target Milestone: ---
Assignee: Tomcat Developers Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-04-10 20:56 UTC by Ryan Lubke
Modified: 2004-11-16 19:05 UTC (History)
1 user (show)


Attachments
Possible fix for this issue. Worked in our env. (1.12 KB, patch)
2002-04-10 21:11 UTC, Ryan Lubke 		Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ryan Lubke 2002-04-10 20:56:37 UTC 
QueryTagSupport.doStartTag() does the following: 
        try {
            maxRows = Integer.parseInt(
                pageContext.getServletContext().getInitParameter(MAX_ROWS));
        } catch (Exception ex) {
            maxRows = -1;
        }

This results in the maxRows attribute being ignored.
Comment 1 Ryan Lubke 2002-04-10 21:11:04 UTC 
Created attachment 1517 [details]
Possible fix for this issue.  Worked in our env.
Comment 2 Justyna Horwat 2002-04-10 21:51:13 UTC 
Fixed.