VAJAVA V3.5.3 TestEnvironment and Debugging - its easy

Hi.

When you open up the WTE console (by starting the WebSphere Test
Environment) you have configuration options.  1 option for the servlet
engine allows you to run the servlets and JSPs INSIDE of VisualAge.  When
this happens, breakpoints you sent in coded or generated servlets will halt
nicely.  You can also add breakpoints in Java beans.  It's easy to inspect,
debug and even change code at runtime here.

In addition there is a JSP execution monitor that shows the execution of a
JSP line by line with the matching generated servlet code.  You can debug
the generated servlets directly but the execution monitor makes it easier
to map back to your JSP code during debug.

You can also run servlets outside of VisualAge and still halt at the start
of the service method.

The last option is to use IBM's distributed debugger tool externally to
debug servlets etc.  This is NOT as simple as VisualAge debugging but can
work too.


Jim Mason

Message text written by INTERNET:java400-l@midrange.com
>
Is it possible to activate debugging of classes/servlets in VaJave-TE ?

I can load and debug JSP's in VaJava-TE.
Now, I also want to debug one of the servlets used in my application.

I tried to add a breakpoint in VaJava IDE but this is of no help.  I
presume
because the application is executed with classes moved to the folders
of TE and not with classes inside VaJava.  Is there any way around this?


<