Since IBM has announced VAJ 4.0 will be the last VAJ, I have been looking for a replacement IDE. I have tried: JBuilder 6.0 Together Control Center 5.5 Visual Cafe 4.5.2 WSAD & Eclipse 4.0 IMHO, VAJ is still the best. The only complaint that I have ever had is the lag in keeping current with the latest JDK and EJB releases, however after working with the above list of IDEs I would gladly accept the lag. For me, the strength of VAJ is built in WTE. The ease of setup and the debugging capability is second to none. I guess it is a mute point... I'll miss you VAJ...
well I really miss the fact that when you made changes while debugging, the editor would start again at the beginning of the method, also the recompilation of jsps in wsad when in debug mode is rediculously slow. and I have a 2 gig cpu with 2gigs of ram/ Even setting breakpoints maxes out my cpu. Althought the deployment process is far better than that of vaj (which makes the it worth using) it has made my development time at least triple. IMHO its like they tried to put way too many bells and whistles and its just a hog, if it was fast I would love it.
posted 17 years ago
The ability to do changes in the debugger was actually due to the fact that we had special hooks in the VAJ JVM. We managed to twist Sun's arm and get this put into the JVM specification for JDK 1.4. When WebSphere will support JDK 1.4 (probably WAS/WSAD 6.0) then this feature will return. Kyle
thats great news do you have any tips for improving the performance of wsad 5? I try to keep projects I am not currently developing closed, but are there any other tips/tricks or config ideas that could help speed thing up? thanks in advance Jesse
Originally posted by jesse harris: are there any other tips/tricks or config ideas that could help speed thing up?
Foremost (this isn't really config, but it's true) is to add memory. Lots of memory.
Second (and I seem to remember hearing Kyle say this at DWLive! last year ) is to turn off the auto-build on resource modification. there's no sense rebuilding when you're hitting save just to avoid losing 5 lines of code that it took 30 minutes to get the logic right, and have 5 more to write. Yes, I'm exaggerating, but still, I save often while mid-work. Also keep your open perspectives to a minimum. You probably only need the Java or J2EE perspective open once you have your test sever set up. You can always open the server view if you need to stop or start the server often. Window->show views->servers
"Write beautiful code; then profile that beautiful code and make little bits of it uglier but faster." --The JavaPerformanceTuning.com team, Newsletter 039.