Difference between revisions of "Web Tools Platform Release 3.0 JavaEE Requirements"

Revision as of 13:28, 25 July 2007

This page will consolidate Java EE related requirements for WTP 3.0 This list will be used form a 3.0 component plan

All requirements should eventually have backing bugzilla entries.

* Deployment descriptor editor(s) for all Java EE 5 DD files.
* Navigator(Project Explorer) content for Java EE models
* Allow up-level spec version changes for JEE facets [1]
* JEE 5 module-specific validator support
* Simplify DD model APIs
* Extensible EE5 model framework that supports merged view of DDs

and source annotations (similar, at least in purpose, to what SAP had initially proposed)

* EJB3 Session/MDB Wizards

== Dependency Management/Virtual Component API/Project Model Reqs/Enhancements

* P? Support facet-based constraints on project module dependencies

[2] (need to determine exact use cases)

* P? Classpath entry publish/export enhancements:
  * Use classpath entry publish/export support to handle most J2EE

dependencies [3]

  * J2EE Module Dependencies UI for utility projects referenced only by

dynamic web projects [4]

  * Support for project cp entries

[5]

  * Support for class folder entries

[6]

  * Others: preferences

[7], quick fix improvements [8]

* P3 Public wrapper APIs for specific module types (e.g. IWebProject,

IEnterpriseApplication) [9]

   * Java EE 5 models - the models must be upgraded to handle Java EE 5 without ANY API breakage. Existing clients MUST continue to work without recompilation. If existing clients are recompiled with the new model, then compilation errors MUST NOT occur (note: we assume that existing clients will not break in any way if they only use the published API - code that relies on internal interfaces MAY break)
   * JSR 175 - support Java EE 5 specifications for annotation based programming, e.g. for EJB 3.0, JPA, Web services
         o JSR 181 - Web Services
         o JSR 220 - EJB 3.0, JPA 
   * validate a JEE5 project (help wanted)