1. I strongly encourage use of IntelliJ IDEA for everything 'cept GUI dev (which is why the #2 monitor has netbeans maximised right now). Its refactoring is so good I cant go back to anything else. And yes, you can debug servers by attachment, as well as running tomcat's main.
2. I am of the view that rather than directly debug your server, or even debug through log files, debug-through-tests is better, as you get regression tests in the process. That doesnt mean that you dont need a good debugger, just that writing tests to replicate a problem, and then more tests to track it down, pays off long term. This is a marked contrast to the old win32 days, when half my app was written in edit-and-continue mode on the debugger; at least all the complex algorithms and low level stuff. Ways to test your web app -junit of the stuff that doesnt need the app server -httpunit: junit extensions for http pages (httpunit.sf.net) -Cactus (jakarta.apache.org). Testing of components deployed on your web server -wsdl2java generation of unit tests. I'm thinking seriously about writing something to create NUnit tests from .NET wsdl proxies, so I can interop test better. ----- Original Message ----- From: "Markus Frommherz" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, January 14, 2003 13:50 Subject: Antw: RE: JBuilder debugging of server side? Which (JB8, I offically have to use it, arghh, but prefer vi).. ) is not too well integrated with ant (try importing (project from existing code) that allready has webapp-structure). IMHO:log4j is the recommended tool anyway. Cheers, markus frommherz >>> [EMAIL PROTECTED] 14.01.2003 22.34 Uhr >>> You should note, however, that with JBuilder 8, Borland's restricted this feature to the startlingly expensive Enterprise Edition, available for something on the order of $2500. > -----Original Message----- > From: Calvin Smith [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, January 14, 2003 4:19 PM > To: [EMAIL PROTECTED] > Subject: Re: JBuilder debugging of server side? > > > I use Jbuilder 6 with websphere 4 > Debugging is easy, I simply: > - set a breakstart > - start websphere with debugging enabld > - tell JBuilder to go attach itself to websphere > - send a soap request > - wait till JBuilder traps the breakpoint > - do whatever > > NOTE: > if your using tomcat then you can simply tell JBuilder > where the main > class is for tomcat and then hit - step into - > > > ----Original Message Follows---- > Is anyone out there using JBuilder to develop their server-side SOAP > code? Any suggestions as to how to set things up to allow > debugging of > server-side code using JBuilder? > > > -Roy > > > _________________________________________________________________ > The new MSN 8: smart spam protection and 2 months FREE* > http://join.msn.com/?page=features/junkmail > >
