Our changes are things like diagnostic trace/logs, which we can't have
permanently switched on for performance reasons. We might want to switch them
on, occasionally, at a customer site.
Indeed, we don't want to have them permanently present in the JSP at all (i.e.
convert the pre-processing
From: Edward Hibbert [mailto:[EMAIL PROTECTED]
Indeed, we don't want to have them permanently present in the
JSP at all (i.e. convert the pre-processing into a run-time
check), also for performance reasons. That was the original
motivation for making this stuff pre-processed.
If you
Have you considered using the assertion facility in the Java 5.0 compiler?
Daron.
-Original Message-
From: Edward Hibbert [mailto:[EMAIL PROTECTED]
Sent: Monday, 18 July 2005 7:38 PM
To: Tomcat Users List
Subject: RE: Preprocessing JSP pages
Our changes are things like diagnostic trace
- which the replies so far suggest - then fine.
Edward.
-Original Message-
From: Peter Crowther [mailto:[EMAIL PROTECTED]
Sent: 18 July 2005 11:12
To: Tomcat Users List
Subject: RE: Preprocessing JSP pages
From: Edward Hibbert [mailto:[EMAIL PROTECTED]
Indeed, we don't want to have
JSP pages
Have you considered using the assertion facility in the Java 5.0 compiler?
Daron.
-Original Message-
From: Edward Hibbert [mailto:[EMAIL PROTECTED]
Sent: Monday, 18 July 2005 7:38 PM
To: Tomcat Users List
Subject: RE: Preprocessing JSP pages
Our changes are things like
,
Daron.
-Original Message-
From: Edward Hibbert [mailto:[EMAIL PROTECTED]
Sent: Monday, 18 July 2005 7:54 PM
To: Tomcat Users List
Subject: RE: Preprocessing JSP pages
I'm not sure what you mean. Throwing an assertionerror exception? Why
would I do that (for something like this) rather
