Community
Participate
Working Groups
For JSF 2.0 forward-looking support in Galileo we will move Facelets support the incubator into an optional PDL support for the new Facelet support in the JSF 2.0 specification as an alternative to using JSP.
We are deferring this feature since the JSF 2.0 spec will not be released in time for the Galileo release. We will consider this feature for a follow-on release of WTP.
Is work going to start back up on this feature for the 3.2 release?
(In reply to comment #2) > Is work going to start back up on this feature for the 3.2 release? > No, we are not planning to work on it for 3.2. We might plan for the Helios release.
Since AFAIK 3.2 will be actually released with Helios, I didn't quite understand what are the current plans. Do you have any ideas or plans when it could start again and when at least the beta version will be ready for testing?
We are going to update the features in the the JSF Facelets Incubator project to be compliant with the JSF 2.0 spec. and release it as part of WTP in the Helios release. We plan to start working on this in December, 09. We will publish more details on the exact feature set and the target milestone once we complete our review of the JSF 2.0 spec.
(In reply to comment #5) > We are going to update the features in the the JSF Facelets Incubator project > to be compliant with the JSF 2.0 spec. and release it as part of WTP in the > Helios release. When are you going to put the JSF Facelets Incubator project plugins into the build? The validation and content assist seem basically working. If you put the plugins in the build earlier, we can find problems earlier.
> When are you going to put the JSF Facelets Incubator project plugins into the > build? The validation and content assist seem basically working. If you put the > plugins in the build earlier, we can find problems earlier. We are currently focusing on 3.1.2 bugs. Once we get past that (end of Jan) we will move forward on JSF 2.0 stuff. If I'm able to get to it sooner, I will update this bug.
Would it be possible to consider targetting this bugzilla to M6 as it is a base feature for JSF 2.0/Facelets support. We have a number of adopter features that plug in into the validation and content assist framework provided by this.
Hi, It would be great to have a better sense of the schedule and features list for JSF 2.0 support in Helios. I've been working on a Java EE 6 GlassFish v3 support for Eclipse and our Tools Bundle is including a modified facelet plugin support to enable at least facelet support. What is not working so far for us is now CDI code completion and JSF 2.0 composite component and annotated managedbeans in jsf page editor. I see there is a talk at EclipseCon regarding JSF 2.0 and myself has a talk on Eclipse and Java EE 6 support with GlassFish. I think it is about time to better coordinate activities there and combine the power of the JSF 2.0 Eclipse support with the GlassFish runtime. EclipseCon would be a perfect time for showing the working in progress there. Ludo (now an Oracle engineer, working in the GlassFish team on Tooling support and other topics).
Message posted to the mailing list: The JSF Tools Project team has posted a requirements document which covers the support for JSF 2.0 in the WTP-Helios release. We have also targeted the corresponding bugs to the upcoming 3.2 M6, 3.2 M7 WTP milestones and will raise new ones as needed. Please review and give your feedback by raising new bugs in bugzilla. JSF Tools Helios Requirements: http://wiki.eclipse.org/Helios_Requirements JSF 2.0 Bugs – https://bugs.eclipse.org/bugs/buglist.cgi?classification=WebTools;status_whiteboard_type=allwordssubstr;query_format=advanced;status_whiteboard=JSF%202.0;bug_status=NEW;bug_status=ASSIGNED;bug_status=REOPENED;product=Java%20Server%20Faces
Created attachment 161052 [details] Address basic issues to bring Facelet incubator into JSF This patch makes the Facelet incubator workable for JSF 2.0. Note that the patch is still against the incubator and requires what is at HEAD in JSF tools. We will commit to JSF tools for next week's M build and then completely retire the incubator.
The incubator code has been committed to HEAD (3.2 M6). The facelet.core and facelet.ui have been left in tact, but may be partially or wholly moved into jsf.core and jsf.ui. facelet.core and facelet.ui are retired in the incubator codeline. The metadata in facelet.tagsupport has been copied into standard.tagsupport. the facelet.tagsupport is retired in all codelines. Once the plugins have been added to the JSF feature and we have a successful build, this bug will be marked fixed. This should happen later today or early tomorrow.
Are you going to introduce a facelet facet? I think I see one in facelet.core plugin. If so, it should be added to JSF2.0 preset, since facelets are the technology of choice for JSF2. On the other hand, can we forgo the new facet all together (so that we don't introduce new facets at all) and just assume that jst.jsf version 2 means facelet development? The less facets the less confusion to the end user and the less maintenance headache going forward (facets can practically be never removed once introduced).
(In reply to comment #13) > Are you going to introduce a facelet facet? I think I see one in facelet.core > plugin. No, the intention is not to have a separate facet for JSF 2.0 Facelets. I have left the old Facelet 1.x facet in tact but it's most likely to be removed. The only reason I can see to keep it is if we decide it's worth having backward compatibility for 1.x tooling; a separate facet would be useful for managing any additional Facelet 1.x libraries.
This got yanked from the distributed feature at the last minute due to a minor build breakage. We don't the ability to fix, so this will move to next week's Ibuild.
Should not the basic issues, such as presence of the facet, be resolved first, before including the plugins into the build?
We have verified that the basic functionality has been added to M6.
