OSNews

While it looks like you could go with IntelliJ, NetBeans or JBuilder, let's take a closer look at actually using the application for web development.

1. Choose an IDE that doesn't require lots of system resources. You want to watch out for IDEs that are developed primarily for Java GUI applications and tend to be sluggish in response when working with web application source code. Even with a powerful processor, Eclipse, JBuilder and NetBeans are sluggish which can quickly reduce your overall enjoyment and decrease productivity. This means that the interface is unresponsive when using menu items, panels and entering code. IntelliJ IDEA and JEdit maintain a high-level of responsiveness throughout.
2. Expect to quickly be up and running with your existing source code. When you need to code the last thing you want is trouble from your IDE. Eclipse, IntelliJ IDEA, JBuilder, and NetBeans have wizards for creating and importing projects around your existing files, however some are outright challenging. Eclipse is the most difficult in this regard and has a steep learning curve. IntelliJ IDEA, JEdit, and NetBeans can use your existing source code directory without a tedious import process.
3. Choose an IDE that enhances your coding experience with the types of files you use everyday. Since web development includes coding Classes, Servlets, JSPs, Tag-Libs, JavaScript, Ant build files, SQL scripts, and web application descriptor files, you will certainly need a tool that can check for errors and highlight the syntax in those files. IntelliJ IDEA does a superb job of real-time error-detection and syntax highlighting in JSPs. You will be amazed the first time you forget to add a tag-lib or import directive and your source code is immediately highlighted with errors. Other IDEs require that you manually compile the JSP before you see any errors.
4. Choose an IDE that integrates well with your source code repository. This one is critical. Make sure you can quickly and intuitively checkout code, update code and compare code. CVS is a popular choice for software development, so I'll use that as an example. In NetBeans trying to configure "External" and "Internal" CVS commands is confusing while IntelliJ incorporates a first-class CVS utility that is tightly integrated. Merging and comparing hundreds of files in a single session becomes extremely rewarding because it's so easy to do.

A Clear Choice

After continually evaluating the various products and being frustrated with the feature-set for Java web applications, it's a pleasure to have come across IntelliJ IDEA.

Here's what makes IntelliJ IDEA so exciting:

• Working with existing code is quick and painless since the IDE is very responsive and uses existing source directories
• CVS integration is highly accessible and more sophisticated than the other implementations; you will no longer need to switch back and forth between the IDE and a dedicated CVS client for complex merging
• Code is immediately analyzed every time a file is opened and the IDE gives prompt indication of warnings, errors and suggestions even in JSPs
• Ant scripts can be mapped to your project and executed in the background
• IntelliJ IDEA is easy to install and works on any Java platform, including Linux, Mac OSX, and Windows, allowing you to change platforms as necessary

It's also the little things and the attention to detail that will make you more efficient. Here's what I like best:

• As you work locally on a file, IntelliJ IDEA will display the lines that have changed, inserted or deleted and allow you to see the previous lines just by moving your cursor over the indicator of the changed line; this is independent of having access to CVS
• If a method that has not been implemented is specified in code, then a single click will add that method to the appropriate Class; you'll know this because IntelliJ IDEA tells you
• A copy/paste buffer allows you to copy all you want, then paste back any copied code using a content selector
• To duplicate a line, block of text, or whatever you have selected, press a hotkey
• Code formatting and import statement optimization can be done automatically when checking code in or manually if you prefer
• If you decide that a variable would have been better then repeatedly using an accessor method, let IntelliJ IDEA introduce a variable and make the necessary changes, with your approval
• If you decide to rename a variable, IntelliJ IDEA can display a list of what code is affected and let you choose if the variable should be renamed in all of those instances
• If you paste a code fragment that references a Class that has not been imported, a dialog asks if an import statement should be created, even in JSPs
• The colors, icons, panel layout, and the simplicity of the menus additionally make this IDE worth using

1. "Page 1"
2. "Page 2"
3. "Page 3"