Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

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

Line 1: Line 1:
This page will consolidate Java EE related requirements for WTP 3.0  This list will be used form a 3.0 component plan
+
This page will consolidate Java EE related requirements for WTP 3.0  This list will be used to form an initial 3.0 component plan
  
All requirements should eventually have backing bugzilla entries.
+
All requirements will eventually have backing bugzilla entries.
  
 
= Java EE5 Requirements =
 
= Java EE5 Requirements =

Revision as of 14:09, 25 July 2007

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

All requirements will eventually have backing bugzilla entries.

Java EE5 Requirements

  1. Deployment descriptor editor(s) for all Java EE 5 DD files.
  2. Navigator(Project Explorer) content for Java EE models
  3. Allow up-level spec version changes for JEE facets [1]
  4. JEE 5 module-specific validator support
  5. Simplify Java EE DD model APIs
    1. Existing model clients MUST continue to work without recompilation(Legacy models in JEE5 projects)
    2. Extensible/Pluggable EE5 model framework that supports merged view of DDs and source annotations
    3. Public wrapper APIs for specific module types (e.g. IWebProject,IEnterpriseApplication)[2]
    4. Public Utility classes
  6. Framework for Archive import that allows pluggable implementations for module type descrimination.
  7. EJB3 Session/MDB Wizards
  8. JSR 175 - Java EE 5 specifications for annotation based programming, e.g. for EJB 3.0, JPA, Web services
    1. JSR 181 - Web Services
    2. JSR 220 - EJB 3.0, JPA

Dependency Management/Virtual Component API/Project Model

  1. Support facet-based constraints on project module dependencies [3]
  2. Classpath entry publish/export enhancements
    1. Use classpath entry publish/export support to handle most J2EE dependencies [4]
    2. J2EE Module Dependencies UI for utility projects referenced only by dynamic web projects [5]
    3. Support for project cp entries [6]
    4. Support for class folder entries [7]
    5. Preferences [8]
    6. Quick fix improvements [9]

Back to the top