NetBeans support for Java 2 Enterprise Edition (J2EE) is something that at least one Canadian-based enterprise development firm is anxiously awaiting, as Sun Microsystems recently rolled out the first beta version of its integrated development environment (IDE), NetBeans 4.0.
The first beta of NetBeans 4.0 does not include support for J2EE, which is used for building enterprise-wide back-end applications.
To date, NetBeans has only supported Java 2 Platform Standard Edition (J2SE), but NetBeans said it would release a J2EE module collection as a separate download for NetBeans 4.0, beta 2. This would extend the NetBeans IDE web-tier development capabilities, allowing for web services development.
David Green is chief technology officer for Make Technologies, a software development company with a standards-based automation approach for software development used by enterprise organisations and developers. He said the J2EE module for NetBeans would boost developer productivity.
"It will make a big difference for enterprise developers," Green said. "Typically, a developer will have to build all the [J2EE] components by hand and that is a time consuming process… but from what is promised, I expect to see productivity improvements in [the J2EE] area. To get any automation in that area makes a big difference."
NetBeans said the J2EE module would be released in October, but for now the community group, which was made open source by Sun in 2000, is touting the productivity and programming improvements to 4.0.
Highlights of the new release include language feature support for J2SE (code named Tiger) and Ant-based projects. Ant is a project system based on Apache Ant that automates the build process of an application and is an open architecture that third-party modules can extend to support current and future types of Java applications, NetBeans said.
The new beta will also include Mobile Information Device Profile (MIDP) support for Java 2 Platform, Micro Edition (J2ME). MIDP is a set of J2ME application program interfaces that define how software applications interface with mobile phones and pagers. It is available as a separate download.
Also included in NetBeans 4.0 is Java refactoring. Refactoring allows developers to make changes to their code without affecting functionality. The refactoring in NetBeans IDE 4.0 provides features such as renames, move class, rename package, change method parameters, encapsulate field and find references, NetBeans said.
"As you are building a system, the nature of your understanding of the problem changes as you progress in the implementation. So usually, you figure out part way through that you can reorganise code differently to make it more understandable," Green said.
"[Refactoring] significantly changes how maintainable the code is, makes it easier to understand for other developers and makes it easier to make enhancements or changes to the system."
In essence, it reduces development time, he added, because refactoring by hand is detail-oriented and time consuming.
Make Technologies not only develops on NetBeans, but also makes a plug-in for NetBeans that automates building J2EE systems, Green said.
The company is currently IDE-independent, and is not exclusively a NetBeans supplier, but also supports Eclipse, Green said.
While Green said the fact that NetBeans is open source is a driving force for his company to use the IDE, he explained that having supplier support for the IDE is also important.
"The fact that Sun stands behind it is great," he said. "The community around the IDE is also a big factor for us."
NetBeans is an open-source, multi-platform product that is available on Solaris, Windows, Linux and Macintosh. Sun, the NetBeans project sponsor, has been in the news recently after Eclipse, an open-source consortium that supports development in other languages, was made open-source by IBM.
Many people within the open-source community have been calling upon Sun to make its NetBeans IDE work with the Eclipse IDE.
Sun has not yet made a move to make both Eclipse and NetBeans work together.
Allison Taylor writes for ITWorldCanada.com
This was first published in September 2004