Community
Participate
Working Groups
As part of the Servlet 3.0 specification for Java EE 6, a web fragment can be developed. One or more of these fragments being combined by way of (what WTP considers) a Dynamic Web project to form the full Servlet 3.0 module. The first step to adding the tooling support for this part of the specification is to define the web fragment facet and an initial facet version.
Created attachment 158806 [details] Patch This patch adds the following functionality: 1. Required facet definition, 2. the install and post install delegates, 3. The project creation wizard and associated infrastructure, 4. API on JavaEEProjectUtilities to query if a project is a web fragment project, and enhancing existing API to support this new project type
Created attachment 158811 [details] Junit Patch Patch contains Junits that test the web fragment code.
Created attachment 158814 [details] Updated Patch Updated patch to refactor properties classes to non-ui plugins. This patch contains the Junit patch as well.
Doesn't WebFragmentFacetInstallDelegate run the risk of having the ModuleCoreNature in there twice? And the execute() method looks a little strange on the lines that read: + if (container != null) + createWebFragmentFile(project, fv, container, monitor); + createManifest (project, container, monitor); ...bad formatting, or a problem waiting to happen?
Created attachment 158817 [details] Updated Patch Thanks for the catch...updated the patch so that null check applies to both method calls. Just tested the addition of ModuleCore nature - it seems to be added only once.. Updated patch attached.
Committed to HEAD for WTP 3.2 M6