Community
Participate
Working Groups
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.
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.
Created attachment 230662 [details] Update the templates and model providers to support Java EE 7
approved
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.
Committed to master for WTP 3.5.0 RC1
*** Bug 407939 has been marked as a duplicate of this bug. ***
*** Bug 407844 has been marked as a duplicate of this bug. ***
*** Bug 406399 has been marked as a duplicate of this bug. ***