The release of the Eclipse Web Tools Platform (WTP) Version 0.7 in July 2005 marks a significant milestone in open source web and J2EE development. The WTP project, seeded by contributions from the IBM Rational Application Developer for WebSphere and ObjectWeb Lomboz, provides a set of well-rounded and tightly integrated tools that simplify the creation of often complex web and J2EE applications. These tools also form the foundation of an integrated web and J2EE tools platform that offers great flexibility to vendors who want to add their own extensions and customization.
The WTP is a new Eclipse top-level project, released for the first time on top of Eclipse 3.1, that contains tools and a platform that support both web and J2EE development. The WTP consists of two subprojects: Web Standard Tools (WST) and J2EE Standard Tools (JST). The WST project contains tools for programming-language-neutral standards such as HTML, XML, and web services. The JST project contains tools specific to the Java language and its J2EE platform such as EJB, servlet and JavaServer Pages (JSP), and Java web services.
The WTP project has three key goals that speak directly to its tools‘ users and platform extenders.
The WTP 0.7 release includes tools for:
From a web and J2EE platform perspective, the second part of Goal 3 is a platform-quality API. This goal is targeted for the 1.0 release-- seeFrom WTP 1.0 to 0.7 and Back Again for an explanation. The WTP API will define WTP as a platform and allow independent software vendors (ISVs) to develop their own enhancements to the Eclipse web tools.
When adopting an open source project, ISVs should primarily consider longevity. With companies such as BEA, IBM, and Oracle already committed to the WTP, the platform already has the support it needs to last a long time.
The first release of WTP provides a well-integrated and easy-to-use development environment for web and J2EE developers of various levels of experience. It makes the tasks of development, testing, and deployment of web and J2EE applications, which can be rather complex, straightforward for developers not deeply immersed in J2EE specifics. Consider a typical J2EE application that provides both business-to-business (B2B) and business-to-client (B2C) services. Figure 1 illustrates how such applications can be architected.
For simplicity and scalability, a typical application will use a database management system (DBMS) for data storage. An Enterprise JavaBeans (EJB) component together with a Java database connection (JDBC) driver can be used to access data from the DBMS. To satisfy the B2B requirement, the EJB component can be exposed as a web service to achieve a platform-neutral and highly interoperable integration point. Finally, the presentation layer between the application and clients can be implemented using a combination of HyperText Markup Language (HTML) and JSP technology. Such an application may look complex on the outside, but using the WTP you can develop it quickly and without a great depth of knowledge about all of the technologies mentioned above.
The WTP is equipped with vendor-neutral tools that allow developers and administrators to manage their data through the use of JDBC drivers. The currently supported DBMSs include Apache Derby, IBM DB2 Universal Database, IBM Informix, MySQL, Oracle Database, Microsoft SQL Server, and Sybase, but any vendor can contribute to WTP by plugging in its own DBMS adaptor. The WTP provides a connection wizard to create live connections to a DBMS. With a connection established, you can view database elements such as tables, stored procedures, and user-defined functions, and update table content using the Database Server Explorer, shown in Figure 2.
You are the WTP community. The only way the WTP will fulfill the community‘s goals is if you provide feedback through bug reports and newsgroup postings, and provide other contributions such as code, documentation, and promotion, where you can. WTP 0.7 contains industrial-quality end user tools and is a good candidate for independent software vendors to explore as a basis for extension. With the community‘s help, the WTP will continue to improve, adding new tools and API, and allow Eclipse to lead the way as the open source web and J2EE development environment.
Jeffrey Liu is a software developer at the IBM Toronto Lab, and a committer for the Eclipse Web Tools Platform (WTP) project.
Lawrence Mandel is a software developer at the IBM Toronto Laboratory, and the lead of ecosystem development and a committer for the Eclipse Web Tools Platform (WTP) project.
聯(lián)系客服
