Lately it seems there is a growing trend of people abandoning Eclipse and moving to Netbeans (or at least the Netbeans bloggers seem to give you this impression by repeating each post they see on multiple other blogs). I guess developers usually do it because they are looking for a more complete environment out of the box with things like J2EE support, Visual Swing development, code profiling etc.
I think this is a mistake, and I urge people to not leave Eclipse for Netbeans!
Leave Eclipse for JDeveloper !
Hear me outÃ¯Â¿Â½
If the reason that you are leaving Eclipse is in a search for a more complete IDE, than don't do the knee-jerk move of switching to Netbeans, take your time to look at one more option JDeveloper, it also costs $0, like Netbeans but it offers much more out-of-the-box. Let me list some of the things here.
First in the J2EE aspect:
- EJB creation with support for the emerging EJB 3.0 standard, including generating entity beans from tables, and generating faÃ�Â§ade interfaces to the beans.
- JSF - with visual JSF page editing, visual JSF page flow editor, a set of over 100 JSF components (ADF Faces), and the ability to use any standard JSF component. (Think about it as Creator and netbeans in one tool).
- JSP - again visual JSP/HTML editing with full support for tag libraries in the component palette. (and of course code insight, debugging etc).
- Struts - Visual Struts page flow editing. (not just code insight into the XML).
- Deployment - Easy one click deploy to Jboss, WebLogic, Tomcat and Oracle Application Server. Dialogs to create and configure J2EE deployments like EAR and WAR.
Embedded J2EE server for testing and debugging your J2EE components (including JSF/JSP debugging).
- Web services - create JAX-RPC web services from any class, visual WSDL editor, Java class generation from WSDL, SOAP messages monitor, WS-Security and WS-Management settings and much more.
Next in terms of agile development functionality:
- Refactoring -Over 35 refactoring options.
- CVS support - including visual merge for conflicts.
- Ant - Ant build file creating with code insight and component palettes, run tasks from inside the IDE and use the color coded log window with links to code.
- Junit - integrated Junit runner, create tests, run, and navigate directly from the log window to the problematic error.
And maybe you need Application Monitoring
- Memory Profiler - Monitor memory consumption and classes in memory heap at time-intervals.
Event Profiler - Check the length and frequency of specific events in your code.
- Execution Profiler - Locate which methods are executed the most.
Or Code Monitoring
- Code auditing with lots of built in rules and the ability to add your own rules (and run audit as part of your Ant build)
- Code Metrics - check the complexity of your code
Code Coach - get advise for optimizing your code
There are some Extras also
XML support including:
- XML editing framework (code insight, structure pane, component palette for any XSD or DTD based XML file)
- Visual XML schema editor
- JAX-B, XPATH, and Xquery support.
- Class, Activity, Use-case and Sequence diagram
- Java class modeling with forward/reverse synch with the code
- Sequence diagram generation while debugging
- Database modeling with forward and reverse engineer
- Database objects creation
- PL/SQL editor + debugger
And much more...
So do yourself a favour, before you switch from Eclipse check one more IDE so you won't need to switch from Netbeans to JDeveloper later on.
Get JDeveloper here