Hi! > > Another really important question.How is possible to trace > > the flow of the framework when i need to debug it? The tomcat > > console is very painful and not every message is put on it. > > Is there a way to attach a visual debugger to dbforms to > > understand better how it works? If I could trace I can > > understand how to correct bugs like the above. Plese, send me > > some info about this topic. > > No problem. I use eclipse to debug dbforms. Just create a tomcat > application, delete the dbforms.jar file and copy all sources of dbforms > into the WEB-INF/src path. > So you can debug everything.
My .02e: usually I use log4j statements a lot: take the code from cvs and fill the method with logger.debug | info stuff. I think it's a faster process. But the programmer should have a bit of knowledge about the code he's tracing (hope the user guide's UML diagrams could help). For jsp, it's another story: ---- servlet specs 2.2 ---- if you try to catch an exception into a jsp page, there's the possibility that the informations you could get are quite useless - IMHO. But if that exception is an "instanceof" ServletException class, it has got the java.lang.Throwable getRootCause() method that returns the "real" exception class, usually containing the message and stackTrace information related to the root problem of your application. --- jsp specs 1.2 (Tomcat 4.X) ---- finally the javax.servlet.jsp.JspException (and javax.servlet.jsp.JspTagException) class bring us the getRootCause() method. Regards, Luca ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ DbForms Mailing List http://www.wap-force.net/dbforms
