I'm building servlet and jsp applications using JBuilder 4.0. I really don't have too much negative to say about it. Tomcat is built into JBuilder 4, so
testing jsps and servlets is a snap. My one complaint is that javascript doesn't always seem to work, which can be a pain.
A good corporate reason to use JBuilder with its built in Tomcat, is that developers don't have to be given admin privledges for the web server. With many web servers, the server must be re-started every time a java class (such as a java bean) changes. Using JBuilder, developers can thoroughly test their beans before deploying them to the web server, preventing frequent re-starts.
This has been the issue where I work, with the web admins not wanting everyone and his brother having the ability to start and stop the server. JBuilder addresses this issue.
JBuilder 4 Professional and JBuilder 4 Enterprise both handle jsps. JBuilder Enterprise adds support for developing EJBs.
Also, JBuilder is very popular (with good reason), and therefore you stand a better chance of finding developers who are familiar with it, thereby possibly having less ramp-up time when a new developer comes on-board.
Hope this helps.
J