Bug 363088 - Web fragment project should present JSF facet selection
Summary: Web fragment project should present JSF facet selection
Status: NEW
Alias: None
Product: Java Server Faces
Classification: WebTools
Component: JSF Tools (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: Future   Edit
Assignee: Ian Trimble CLA
QA Contact:
URL:
Whiteboard: other
Keywords: plan
: 489094 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-11-07 14:34 EST by Ram Venkataswamy CLA
Modified: 2018-10-10 18:31 EDT (History)
4 users (show)

See Also:


Attachments
Initial work to support web fragments with JSF features (80.01 KB, patch)
2013-05-22 13:54 EDT, Ian Trimble CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Ram Venkataswamy CLA 2011-11-07 14:34:28 EST
Build Identifier: M20110909-1335

Web fragment project wizard should present JSF facet selection

Reproducible: Always

Steps to Reproduce:
- launch web fragment project wizard

- click modify, the listing doesn't present JSF facet
Comment 1 Ian Trimble CLA 2012-01-23 18:57:16 EST
At present, we have no intention of supporting the installation of a JSF facet on a web fragment project.

A facet applied during use of the web fragment project wizard applies to the web fragment project, and not any web app project that may also be created (so the JSF facet would need to be manually added to a created web app project after the wizard completes).

The JSF facet that we currently have enables capabilities that we do not see as having a useful purpose in a web fragment project, such as JSF authoring. A web fragment project is not a web application, it is essentially a utility project with intelligence to understand web app configuration (in web-fragment.xml and in annotations) such that a consuming web app project merges the configuration into the overall web app model. There is no merging of such things as faces-config.xml, since web fragments are part of Servlet 3.0 and have no relevant counterpart in JSP or JSF specification. JSF pages (JSP or facelets) authored in the web fragment project would not be accessible in a consuming web app project, and so that capability is also not useful in a web fragment project.

For these reasons, we see no reasonable use case that makes applying the JSF facet to a web fragment project worthwhile at this time. We should revisit in the future to see if relevant use cases have evolved as people have started to use web fragment projects.
Comment 2 Dieter Scholz CLA 2013-04-11 11:22:22 EDT
I would vote for the JSF facet option in web fragment projects. Perhaps you should read the following article:

http://ocpsoft.org/java/jsf-java/how-to-modular-jsf-applications-with-cdi-and-prettyfaces/

I tried that with Glassfish and it worked as described. But - in Eclipse - it wasn't possible to use the JSF functions in the module jar project.

Please reconsider offering that option.
Comment 3 Raghunathan Srinivasan CLA 2013-04-11 12:16:39 EDT
We will review for M7.
Comment 4 Ian Trimble CLA 2013-05-22 13:54:01 EDT
Created attachment 231320 [details]
Initial work to support web fragments with JSF features

This is work done so far to support web fragment projects with JSF features. Not all features are 100% functional (for example, one known issue is that managed beans are not located by content-assist when faces-config is in META-INF).
Comment 5 Raghunathan Srinivasan CLA 2013-05-23 14:11:40 EDT
The fix for this involves too many changes and is risky to check in to the Kepler release. We will continue to work on this issue and will get this into the first maintenance release.
Comment 6 Raghunathan Srinivasan CLA 2013-08-22 14:36:56 EDT
Plan for Kepler SR2
Comment 7 Raghunathan Srinivasan CLA 2014-05-27 14:36:36 EDT
Triage: Luna is in ramp down mode. We will review these for the first maintenance release.
Comment 8 Ian Trimble CLA 2016-03-31 16:44:26 EDT
*** Bug 489094 has been marked as a duplicate of this bug. ***