I agree with you T. that using an IDE to set breakpoints, step and watch variables is the preferred method for debugging.
I have used Struts in Visual Age for Java 4.0 for a while now and I have saved SO MUCH TIME in debugging. I have been able to debug and step right through the Struts source, and errors which would have taken hours to find, have taken me minutes. I just can't stress enough how important an IDE can be for a developer. You can save yourself and the company you work for a lot of time and money by being more productive and getting the work out a lot faster by using these tools. I believe that a chapter in the struts book about debugging with an IDE would be a great way to teach people about how much more productive they can be by using these tools, while at the same time making the book more marketable. JDA ********************************************** Juan Alvarado Internet Developer -- Manduca Management (786)552-0504 [EMAIL PROTECTED] AOL Instant Messenger: [EMAIL PROTECTED] -----Original Message----- From: Thinh Doan [mailto:[EMAIL PROTECTED]] Sent: Monday, January 28, 2002 12:34 AM To: Struts Users Mailing List Subject: RE: OReilly Struts book Well if you have to add "log" statements in the code to trace & debug, I'd call the old Fortran method. The new way would be able to use the IDE to step, use breakpoints, and display variables etc... Any tools that can provide these facilities would be of great help in general. If you can just answer "How to debug Struts apps?" in a few pages or so, that'd be helpful. T. -----Original Message----- From: Chuck Cavaness [mailto:[EMAIL PROTECTED]] Sent: Sunday, January 27, 2002 7:31 PM To: Struts Users Mailing List Subject: RE: OReilly Struts book Thanks for the input. I'm doing the 1.0/1.1 dependent chapters last. That will give me time to see when it comes out and how I'm going to cover it. Something on performance is a must. I'm not sure if it's a complete chapter or whether it can fold into another one. Chapter 18 deals mostly with logging and specifically integrating log4j into your web apps. Although logging and testing are somewhat related, I think they would deserve seperate coverage. I'll give the testing methodology some thought. Were you thinking something like JUnit/JTest, that sort of thing? The development environment idea is interesting, although I'm not sure that I could give it adequate coverage. OReilly books tend to be a little smaller than something like Que. It's going to be so fat as is... My idea for appendix A was that it would be similar to the JavaDocs. All of the classes/interfaces with public methods. That sort of thing. Thanks again for the input, Chuck At 04:45 PM 1/27/2002 -0600, you wrote: >Very good TOC, Chuck! Personally, I'd like more focus on Struts 1.1 (since >I've been using 1.0 for a while now) and EJB. Also, a chapter on development >environment, like JDeveloper, JBuilder, Forte, etc. w/ Struts, brief >performance analysis on using Struts w/ Tomcat, JRun, WebLogic, WebSphere >etc... would be great. Finally a chapter on testing methodology with apps >using Struts would be a bonus (or is it chapter 18?). > >Thanks, > >Thinh > >PS: BTW, is Appendix A organized like a Struts reference guide? -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
