Community
Participate
Working Groups
Create a DWP with JSF 2.0 Facet only. Create a XHTML file. Add h:Outputtext Gesture to get content assist for attributes in this tag. Result: No Content Asssit. Now add the Facelet facet Content Assist for attributes of h and f tag work. Other use cases which require the Facelet facet include running the XHTML page on the server.
Requiring user to add both the JSF 2.0 and Facelet facet will confuse end users and this should be fixed for M6.
Was brought up in https://bugs.eclipse.org/bugs/show_bug.cgi?id=251798#c14
(In reply to comment #2) > Was brought up in https://bugs.eclipse.org/bugs/show_bug.cgi?id=251798#c14 Yes but to be clear, if we keep the Facelet facet it won't be to support the Facelet 2.0 Facelet development. It will be to be support the backward compability for users of 1.x in the 2.0 spec. This bug has to do with the fact that the incubator code controlled enablement based on this facet for things like content assist; this is no longer correct.
Fix committed to HEAD (3.2M6).