1.

GUI: The major requirement of today’s developers is to have a good User Interface for
their users. They can provide whatever functionality they need but it’s the GUI that lets
the user better know the existence of that particular functionality and its easier for them
to click and select than type something on a black boring screen. Thus, today’s
developers need IDE’s such as netbeans that develop ready made windows forms with all
the required buttons, labels, text boxes and like that can be tailor made for the program in
question.

2.Database Integration: Database based program developers know how hard it is to

interface your back-end database to your front-end program. This is where netbeans
packs the punch by providing you a CRUD(create, Read, Update, Delete) application
shell. Life’s easy,

Details¶
Some advantages of using the Netbeans Platform are as follows:

 Extensible and easy modular design

 Vast API of commonly used tasks
 Easy to design Swing GUI using Netbeans IDE
 Pre-defined update center and automatic update notification

Advantages of Eclipse

All our Java courseware is designed originally to be used with simple text editors and
command-line tools. This helps us focus on the standards we're trying to teach -- the Java
language, the compiler, various J2EE standards and tools -- and keeps the material
vendor- and platform-neutral.

Still, many students and instructors are accustomed to more productive integrated
development environments, or IDEs. In the Java world, Eclipse has recently emerged as
the clearly dominant IDE: it is powerful, standards-based, and free, developed by an
open-source model. Some of its most attractive features are:
  Syntax highlighting -- notice how Java
keywords, comments and the programmer's
own variable and method names are
distinguished visually in the editor window
shown here
 Proactive error reporting -- the programmer
is advised of compiler errors even while typing new code, and with this
immediate feedback can write clean code more quickly
 Auto-completion features, allowing the programmer to save some typing and find
less familiar field and method names in the Core API more quickly
 Popup windows with API documentation that appear when one hovers the mouse
over an identifier
 Integrated testing and debugging
 Code refactoring features that will carry out intelligent, Java-aware global
replacements of names for variables, fields, methods, classes, and whole packages
of code

Even so, Eclipse is not a universal choice; in fact using any IDE rubs some instructors the
wrong way. (See When to Use Eclipse Overlays for more discussion of how much IDE
use is appropriate.) At Object Innovations we've chosen to make support for Eclipse
available, but not as part of the standard course materials. Rather, we've developed the
Eclipse overlay as an add-on to the lab files for a given course: it is installed, optionally,
after the main lab image is in place, and it can be used independently of the command-
line procedures spelled out in our coursebooks. Instructors and students can even choose
to mix and match their use of Eclipse to carry out one exercise but perhaps use a plain-
text editor and command-line tools to work through another.

What is an Eclipse Overlay?

An Eclipse overlay is simply a file tree containing an Eclipse workspace and one Eclipse
project for each example, demo, or lab exercise in a given course:
With the overlay, an instructor can apply all of Eclipse's power to any or all of the
exercises in the course he or she is teaching. Fans of Eclipse will enjoy the productivity
boost, and many instructors see the auto-correct and feedback features of IDEs as helping
the students learn the Java language more quickly. Instructors and students can code,
build, test, and debug most course exercises entirely from within Eclipse.

Limitations

Eclipse, right out of the box, supports basic Java coding, compiling, and testing very
well. Many of our courses go beyond these skills to advanced techniques and especially
to J2EE technology. This requires more than just compiling source code and running an
application: there are steps to package and deploy applications to Web servers or
application servers; often some form of code-generation is involved. Without a lot of
coaching, Eclipse can't coordinate the packaging and deployment steps; and its eager
evaluation of Java source code winds up reporting a number of "false negatives" on
perfectly viable Java source files, when it doesn't understand that some code on which a
given class depends has yet to be generated -- but will be in place just in time, as part of a
complete build of the application.

For these more complex J2EE structures especially, the tool of choice is Ant -- an XML-
based make utility. OI's courses in J2EE topics use Ant to assure reliable, repeatable
builds so that students can concentrate on coding and testing. Here the usefulness of
Eclipse is usually limited to basic coding and compiling -- still worth doing -- and
integrated debugging typically falls away as Eclipse's debugger can't interact with the
Web server or J2EE server that's hosting the deployed application.

Finally, for some of our courses, Eclipse in its basic form is simply not useful, and so we
don't make overlays available. For instance there is no native JSP editor in Eclipse, so we
don't bother with an Eclipse overlay for our JSP or JSTL courses; the standard Eclipse
SDK will compile J2SE-format class files, and so we don't try to force a fit between this
tool and our J2ME (Java 2 Platform, Micro Edition) courseware.