Louis Tribble wrote:
> "Craig R. McClanahan" wrote:
> >
> > Larry Isaacs wrote:
> >
> > > Hi all,
> > >
> > > We have a need for a global way to have Jasper compile the
> > > JSP servlet source with debug information. I would propose
> > > defining a system property such as:
> > >
> > >
> Getting Tomcat to use the right compiler command to work with our
> debugger has been a headache, both in preparing documentation and
> in providing support. And Tomcat 3.1 and 3.2 have some differences
> besides. I would love to see this configurable in server.xml both
> globally and per contex
"Craig R. McClanahan" wrote:
>
> Larry Isaacs wrote:
>
> > Hi all,
> >
> > We have a need for a global way to have Jasper compile the
> > JSP servlet source with debug information. I would propose
> > defining a system property such as:
> >
> > jasper.compile.debug
> >
> > which if set
> Wouldn't you really want this option at the per-web-app
> level, rather than
> global? While we were at it, you'd want similar options for turning
> optimization on and off, or (more generally) a way to set
> compiler options for a
> generic compiler.
The main need at SAS is for a way to wi
Larry Isaacs wrote:
> Hi all,
>
> We have a need for a global way to have Jasper compile the
> JSP servlet source with debug information. I would propose
> defining a system property such as:
>
> jasper.compile.debug
>
> which if set to "true" would turn on the inclusion of debug
> info.
Hi all,
We have a need for a global way to have Jasper compile the
JSP servlet source with debug information. I would propose
defining a system property such as:
jasper.compile.debug
which if set to "true" would turn on the inclusion of debug
info. Any objections or alternative proper
