I have taken the org.apache.jasper.util.SystemLogHandler Remy wrote
and put it in org.apache.tomcat.util.log.SystemLogHandler.
I refactored it so that the PrintStreams and Byte arrays are recycle.
Plus implemented a stack so that there can be nested usage.
Finally, I implemented it in
Wouldn't this introduce a dependency on Tomcat JARs for Jasper 2? I can
think of at least one project off hand that uses Jasper standalone; it
seems a shame to change this, since Jasper 2 is currently engine-agnostic.
- a.
Glenn Nielsen wrote:
I have taken the
The other problem with logging is that messages logged without a trace
level are not given a default trace level so there is no way to stop
those messages from being displayed. Why are messages not given a
default log level if they are not created with one.
John
-Original Message-
Problem
---
Frequently code running within a web application context will print
to System.out, System.err, printStackTrace(), etc. This output ends
up getting logged to catalina.out without any timestamps. When
you have multiple virtual hosts/contexts it can be a pain to correlate
Remy Maucherat wrote:
Problem
---
Frequently code running within a web application context will print
to System.out, System.err, printStackTrace(), etc. This output ends
up getting logged to catalina.out without any timestamps. When
you have multiple virtual hosts/contexts it can be a
Remy Maucherat wrote:
How is Ant implemented within Tomcat for doing JSP compiles?
I am concerned about Ant running within the same JVM and having to capture
the JVM's System.out and System.err. Other output from catalina could get
intermixed with the Ant output. Also I saw something
Remy Maucherat [EMAIL PROTECTED] wrote:
Remy Maucherat wrote:
How is Ant implemented within Tomcat for doing JSP compiles?
I am concerned about Ant running within the same JVM and having to capture
the JVM's System.out and System.err. Other output from catalina could get
intermixed
However, I'd like to point out that there's no other choice but to upgrade.
In many situations, the current Jasper 2 generated servlets don't compile to
valid bytecode when using the classic compiler (and you get a VerifyError
when loading the class; this happens esp when using JSTL).
Kin-Man Chung [EMAIL PROTECTED] wrote:
However, I'd like to point out that there's no other choice but to upgrade.
In many situations, the current Jasper 2 generated servlets don't compile to
valid bytecode when using the classic compiler (and you get a VerifyError
when loading the
