You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Larry Isaacs <La...@sas.com> on 2000/12/12 05:57:32 UTC

Compiling JSP's with debugging info in Tomcat 3.3

> BTW, another piece of feedback - would it be possible to implement part
> of this as an interceptor ?

I was assuming for Tomcat 3.3 the JSP option properties would be
implemented in JspInterceptor since it is tied to Jasper anyway.  Do you
have more general plans for JspInterceptor that would suggest these
options go in a separate interceptor?

> For the web.xml changes - you can use
> a
> context attribute too.

Since JspInterceptor provides a way to specify these options in
server.xml, I don't have a real need for a context attribute.  I would
add a debugInfo property to Jasper's Options.java and with it
EmbeddedServletOptions.java.  Rather than ignore the debugInfo property,
I would add a "debuginfo" init parameter to EmbeddedServletOptions.java
just so it can be controlled in web.xml, but I wouldn't anticipate using
it.  I think server.xml is a more appropriate place for configuring these
options.

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.

Cheers,
Larry

RE: Compiling JSP's with debugging info in Tomcat 3.3

Posted by Scott Stirling <ss...@mediaone.net>.
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



Re: Compiling JSP's with debugging info in Tomcat 3.3

Posted by "Craig R. McClanahan" <Cr...@eng.sun.com>.
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