Re: JSP stack traces

[Erich Oliphant]

Hi,
Thanks for the info.  I got some code from the resin list that massages 
a pure java stack trace and adds the JSP line # info.  Now I'm trying to 
figure out where to put it :)  Been going thru the Cactus source but 
still not exactly sure of the best place.  Was thinking about some sort 
of interceptor approach in ServletTestCase.runCactusTest().   Something 
where I'd check to see if I have a "massager" for the current container, 
if so run it on the exception then rethrow it.

Erich

BTW, How do I turn on server-side logging ? :)

Vincent Massol wrote:

Hi Erich,

For the line number I have no idea. I would have thought that as Cactus
executes in the container you should get exactly what the container
returns. However, the Cactus client side might loose this information
(not sure). I'd suggest you turn on Cactus logging to get server side
logs.
For the generated servlet files, it is a container configuration. I
don't know how you set it with Resin. In any case, you have the option
of passing a custom resin config file to the <cactus> Ant task (using
the resinconf attribute).
Hope it helps,
-Vincent
 

-----Original Message-----
From: Erich Oliphant [mailto:[EMAIL PROTECTED]
Sent: 08 April 2004 18:18
To: [EMAIL PROTECTED]
Subject: JSP stack traces
Hi,
I am using Cactus (via Ant & Resin2x w/ a ServletTestCase ) on some
'real' :)  JSPs replete with embedded code, etc.  I am planning to
Cactus to drive some of the refactoring.  I have a small problem
however.  I am not getting the JSP line # info in exception thrown by
the JSP but rather the generated servlet.  I believe the containers do
   

a
 

bit of magic to get you the JSP line info when you have an exception
   

in
 

a JSP during normal execution.  Is there anyway to get this to work
during cactus run?  Other problem is that since the temporary
   

deployment
 

of the container gets erased, I can't even go look at the generated
servlet file an work backward from that.
Any Ideas?

Erich

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
   



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]