P.S. If this is as simple as adding a field for this property and a
setter, then I'll go ahead and do this in my own Tomcat distro if
nothing else...
--
Jess Holle
Jess Holle wrote:
Not to reply to my own e-mail but after reading the sources this would
appear to be squarely a Tomcat developer issue.
JspC.isSmapSuppressed() always returns true -- affording no
opportunity to precompile while still generating JSR-45 debug info.
While that's a great default for production, I for one would really
like the ability to set this to false in development so I can
precompile *and* do JSP source level debugging.
Thoughts? [Or is this already in 5.5.12? I'm still at 5.5.9.]
--
Jess Holle
Jess Holle wrote:
Is this a more appropriate question for the dev list?
--
Jess Holle
------------------------------------------------------------------------
Subject:
JSP Precompilation vs. JSR-45 Debugging
From:
Jess Holle <[EMAIL PROTECTED]>
Date:
Thu, 27 Oct 2005 08:45:47 -0500
To:
Tomcat Users List <tomcat-user@jakarta.apache.org>
To:
Tomcat Users List <tomcat-user@jakarta.apache.org>
I have noticed that when I use an Ant script based on that documented
in the Tomcat docs to precompile all my JSPs the resulting JSPs do
not support source-level (JSR-45) debugging.
I thought I was doing something wrong so I looked through the JspC
source code and I can't see how I could feed it anything more
information.
As an added complication I have an extra directory that I need in the
compilation classpath. I have extended the web app classloader to
handle this and added a line to the javac classpath in the Ant
script. Thus things work fine in that respect but I need that to
keep working -- I just want to have an option to do source-level JSP
debugging as well.
What am I missing?
--
Jess Holle
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
