tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott Stirling" <>
Subject RE: Compiling JSP's with debugging info in Tomcat 3.3
Date Wed, 13 Dec 2000 03:51:16 GMT
Hi Craig,

I've known this JSR has been going on for quite a while, but is it more than
pie in the sky?  I thought it was one of those zombie JSRs, like the
standard tag library (JSR-052) and the JSP/Servlet benchmark (JSR-039)... Is
this an active one that you know of?

A big problem with several of the JSRs just in J2EE-land is that there
aren't enough experts to go around; the same people in the industry are
responsible for 3-5 JSRs.  Even if they're on related subjects, there's too
much to keep up with.

Scott Stirling
Allaire Corp.
(Note: Allaire is listed as a member of the expert group on JSR-045 (the
debug non-Java languages one), but I'm not involved)

-----Original Message-----
From: Craig R. McClanahan []
Sent: Tuesday, December 12, 2000 1:07 PM
Subject: Re: Compiling JSP's with debugging info in Tomcat 3.3

Larry Isaacs wrote:

> In addition to specifying these JSP options, I'm looking for a way to
> alter the defaults that get used when these options aren't specified in
> server.xml.  My target is to be able run Tomcat in debugging and
> non-debugging situations using the same server.xml and without modifying
> server.xml to switch. Not having to ask the user to modify server.xml
> helps avoid a potential source of errors and avoids the need to document
> it for someone who might not be familiar with Tomcat.
> So far, my best guess is to support a JSP defaults string like that
> described in the earlier e-mail and obtain this string from a System
> property, or perhaps a command line argument.  My preference would be
> as a System property.

One thing you should keep in mind, on the general issue of debugging
information, is that there is a Java Specification Request (JSR-045)
under way which will standardize mechanisms for storing debugging
for non-Java languages that are translated into Java source code -- JSPs
an obvious example -- into the class files themselves.  Jasper in the 4.x
is going to track the results of that effort when they come out.

You can get more information about JSR-045 at the Java Community Process web
site <>.

> Cheers,
> Larry


View raw message