well, like I already posted here, I use a semi-manual approach.
I use JPadPro to write the code, compile stuff and do the debugging.
works fine for me.
I use apache with JServ and I start JServ in manual mode and use jdb instead
of javaw. that shows me a password. I use the JDB from JPadPro but you can
also use JDB itself.
Instead of the class name I put in the password and I have My debugging
session.
This even works for remote debugging.
Geert 'Darling' Van Damme
> -----Original Message-----
> From: A mailing list about Java Server Pages specification and reference
> [mailto:[EMAIL PROTECTED]]On Behalf Of John Wu
> Sent: vrijdag 10 december 1999 23:55
> To: [EMAIL PROTECTED]
> Subject: jsp step debugging
>
>
> Hi, does anyone one know of a good jsp debugging tool or good jsp
> debugging
> methods/techniques? I've been working with jsp on weblogic server and
> things are working for the most part, but debugging tends to be some what
> painful with just out.print placed all over the place. If there's a step
> debugging tool out there it would be of great help. Thanks.
>
> ==================================================================
> =========
> To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff
> JSP-INTEREST".
> FAQs on JSP can be found at:
> http://java.sun.com/products/jsp/faq.html
> http://www.esperanto.org.nz/jsp/jspfaq.html
>
>
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
FAQs on JSP can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
