Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 400483 - Update Java EE artifact wizards for Java EE 7
Summary: Update Java EE artifact wizards for Java EE 7
Status: RESOLVED FIXED
Alias: None
Product: WTP Java EE Tools
Classification: WebTools
Component: jst.j2ee (show other bugs)
Version: 3.5   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: 3.5 RC1   Edit
Assignee: Carl Anderson CLA
QA Contact: Chuck Bridgham CLA
URL:
Whiteboard: JavaEE7 PMC
Keywords:
: 406399 407844 407939 (view as bug list)
Depends on: 252618
Blocks:
  Show dependency tree
 
Reported: 2013-02-11 14:58 EST by Carl Anderson CLA
Modified: 2013-06-06 03:19 EDT (History)
7 users (show)

See Also:
ccc: pmc_approved? (david_williams)
ccc: pmc_approved? (raghunathan.srinivasan)
ccc: pmc_approved? (naci.dai)
neil.hauge: pmc_approved+
ccc: pmc_approved? (kaloyan)
ccc: pmc_approved? (cbridgha)
cbridgha: review+


Attachments
Update the templates and model providers to support Java EE 7 (8.53 KB, patch)
2013-05-08 12:57 EDT, Carl Anderson CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Carl Anderson CLA 2013-02-11 14:58:30 EST
Currently the wizards for creating Java EE artifacts are not extensible enough - especially in the finish operations. We should ensure that having the basic Java EE 7 support provided by WTP will be enough for adopters to extend the existing wizards in a way that they can be reused for Java EE 7 too.
Comment 1 Roberto Sanchez Herrera CLA 2013-05-03 16:41:12 EDT
I found some problems while testing the creation of some artifacts in I-3.5.0-20130502215817

1. The new Session bean wizard cannot be completed when the project is EJB 3.2 (the Next and Finish buttons are never enabled)

2. The Web 3.1 projects are created by default without deployment descriptor, just like 3.0. But when a servlet is created, the servlet is not annotated and the default deployment descriptor is added.
Comment 2 Carl Anderson CLA 2013-05-08 12:57:48 EDT
Created attachment 230662 [details]
Update the templates and model providers to support Java EE 7
Comment 3 Chuck Bridgham CLA 2013-05-08 13:20:33 EDT
approved
Comment 4 Carl Anderson CLA 2013-05-10 16:08:20 EDT
Explain why you believe this is a stop-ship defect. Or, if it is a "hotbug" (requested by an adopter) please document it as such.

This bug prevents users from creating Java EE artifacts in Java EE 7 projects.

Is there a work-around? If so, why do you believe the work-around is insufficient?

There is no work-around.

How has the fix been tested? Is there a test case attached to the bugzilla record? Has a JUnit Test been added?

The Java EE JUnit test bucket was run, and the changes have been tested by hand.

Give a brief technical overview. Who has reviewed this fix?

The enablement checks for Java EE artifacts for Java EE 6 have been extended to check for Java EE 7.  Chuck Bridgham has reviewed this fix.

What is the risk associated with this fix?

Low - it effects the artifact generation code, but only enhances the enablement.
Comment 5 Carl Anderson CLA 2013-05-14 13:09:12 EDT
Committed to master for WTP 3.5.0 RC1
Comment 6 Carl Anderson CLA 2013-06-04 11:06:36 EDT
*** Bug 407939 has been marked as a duplicate of this bug. ***
Comment 7 Carl Anderson CLA 2013-06-04 11:10:53 EDT
*** Bug 407844 has been marked as a duplicate of this bug. ***
Comment 8 Jesper Skov CLA 2013-06-06 03:19:47 EDT
*** Bug 406399 has been marked as a duplicate of this bug. ***