• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Jsp/Servlets debugger

 
Ranch Hand
Posts: 67
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi all,
I'm looking for a jsp/servlet debugger and I saw that JBuilder, Eclipse and Sun One offer debugging facilities in their respective product. Has anyone been using their debugger facilities? Just want to get some feedbacks. Any other debugging tools worth mentionning? I use tomcat with win2k.
Thanks,
Francois.
 
Ranch Hand
Posts: 2166
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Francois,
there was some discussion recently:
https://coderanch.com/t/355374/Servlets/java/would-best-tool-debug-servlet
There is a french eclipse plugin, but they are still working on it to make it more usable. WSAD has a Tomcat debugger. I only have used the websphere debugger, and its slow.
I aggree with Wiliam Brogden in the mentioned discussion. Best debugger is a programmers brain. If you have your business logic in the JavaBeans you can write them. Test them. When they work, you can write the web-presentation layer. I am following this strategy and I do not miss a debugger very much. You can also use log4u package from jarkarta to get debug messages out of your app (much better than System.out.println(). You can also use System.out.println() and a textpad pointed to the current tomcat log file. Log4u is better and its quite easy to set up.
I think in the netbeans book at O'Reilly they describe tomcat debugging with netbeans.
But as I said. I think one does not need very much a debugger if you have a clean separation of business logic and presentation logic.
Problem arise when your beans needs quite complex object graphs from the users http-session.
regards Axel
 
Always! Wait. Never. Shut up. Look at this tiny ad.
a bit of art, as a gift, that will fit in a stocking
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic