DO NOT REPLY [Bug 13965] New: - Need a way to globally configure Jasper options

[bu...@apache.org]

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=13965>.
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=13965

Need a way to globally configure Jasper options

           Summary: Need a way to globally configure Jasper options
           Product: Tomcat 4
           Version: 4.1.13
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Jasper 2
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: william.barker@wilshire.com


I set up 4.1.13 today, added the enablePooling=false param to 
$CATALINA_HOME/conf/web.xml, and pointed the docBase to my old Servlet 2.2/Jsp 
1.1 application.  Tomcat then choose to compile all of my <jsp-file> servlets 
with the default enablePooling=true, with not very happy results :(.  

I know that there is the work-around of adding the enablePooling=false param to 
all of my <jsp-file> servlets, but it would be nice if there was an easier way 
to do this.

For this particular application, I don't believe that I'll be actually gaining 
(and may even lose) by trading syncs for gc.  I'll still want pooling off even 
after the taglib is lifecycle-compliant.

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>