Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
From: "Scott Stirling" <sstirling@mediaone.net>
To: <tomcat-dev@jakarta.apache.org>
Cc: <sstirling@allaire.com>
Subject: RE: Compiling JSP's with debugging info in Tomcat 3.3
Date: Tue, 12 Dec 2000 22:51:16 -0500
Message-ID: <NEBBJKPJKLBGBGIOBGAGGEPECCAA.sstirling@mediaone.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
In-Reply-To: <3A36693F.5E5F5777@eng.sun.com>
Importance: Normal

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 [mailto:Craig.McClanahan@eng.sun.com]
Sent: Tuesday, December 12, 2000 1:07 PM
To: tomcat-dev@jakarta.apache.org
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)
currently
under way which will standardize mechanisms for storing debugging
information
for non-Java languages that are translated into Java source code -- JSPs
being
an obvious example -- into the class files themselves.  Jasper in the 4.x
tree
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 <http://java.sun.com/jcp>.

>
> Cheers,
> Larry

Craig