Eclipse Web Tools Platform 1.5 - New and Noteworthy

Small WTP logo


J2EE Module Dependencies

The J2EE Module Dependencies property page has been enhanced to allow dependencies to Java projects, jars within the workspace, external jars, and variables to jar entries.


Web projects have the option of defining their dependencies within an EAR if contained, or through Web libraries that are mapped to the modules "WEB-INF/lib" folder.


J2EE Project Explorer View

The view is now based on the new Common Navigator Framework. Click here for more info on the framework. Changes include optional consolidation of Java content that displays source folders, and Java libraries under a single node.


The grouping of J2EE module types (formally specialized working sets) is no longer available

JSR 109 Webservices are shown with menu content (only if detected in workspace projects) in the following node.


J2EE Module Creation Wizards

The first page of the module creation wizards now designates a facet configuration that allows adopters to declare a group of facets that form a feature or configuration for the project.


Binary EAR Import

Additional support for binary modules within an EAR has been added to support team scenarios and avoid excessively large workspaces. The third page of the EAR import wizard displays the module list with its intended Project name. The module checkbox is now available to specify importing the module without creating an Eclipse project, and storing in the EAR project as an archive.


The classpath dependencies are automatically managed, and content of these binary modules are viewed from the EAR projects modules/binary folder


EJB XDoclet Container Managed Bean support

In addition to the existing Session and MDB support, Container Managed Entity 1.x,2.x support has been added through the existing "XDoclet Enterprise Java Bean" wizard.


The CMP attributes can be entered manually, or derived from a live JDBC connection that maps RDB columns to attributes



JSP Fragment settings

The JSP Fragment property page can be used to specify the default scripting language and generated content type for JSP fragments, as well as whether or not to validate Java scriptlets within the fragments.

JSP Fragment property page

TLD Lookup through the XML Catalog

The JSP component now supports locating custom Tag Library Descriptors (TLDs) using the XML catalog. Users can create their own entries using the existing XML Catalog preference page. Adopters providing server adapters should refer to enhancement 129112 for further details.

XML Catalog preference page

Editing a TLD URI entry in the XML Catalog