Community
Participate
Working Groups
This bug is to track an enhancement request add support for Facelets with JSF 1.2 as discussed in the bug 192393: Gerrit Brehmer 2010-10-01 02:39:00 EDT But there is no support for JSF 1.2 & xhtml Facelets Editor with Content Assist in Helios anymore. So for JSF 1.2 Projects I must use Galileo with Facelets Tools Plugin and for JSF 2.0 Project I can use Helios. Because Facelets with JSF 1.2 is still used in many projects, why was this support dropped from the feature list? [reply] [-] Comment 50 Mariusz Smykula 2010-10-01 02:43:47 EDT This bug is about facelets (also in JSF 1.2) not about JSF 2.0. Facelets was used before JSF 2.0 and many projects still are using this combo: facelets and JSF 1.2. [reply] [-] Comment 51 Raghu Srinivasan 2010-10-06 19:15:27 EDT (In reply to comment #50) > This bug is about facelets (also in JSF 1.2) not about JSF 2.0. Facelets was > used before JSF 2.0 and many projects still are using this combo: facelets and > JSF 1.2. There is no plan to support Facelets with JSF 1.2 primarily due to lack of resources. We welcome any contribution to Indigo that will add support for JSF 1.2 and Faclets.We still have Facelets supoprt in the JSF Facelets incubator project.
did this mean that an existing jsf1.2/Faclets/JEE5 Project can not be developed within Eclipse Helios? This would bean that Helios is not for JEE5 developers? I can not belief this. Why is this so a big deal to support the .xhtml files? When I rename my .xhtml file into .jsp code completion works fine. But I was still not able to tell eclipse handling .xhtml files like .jsp files. I added the contentType and assigend the jsp-editor to the .xhtml file extension. But this all did not work. Is there no workaround??
Ralph, As mentioned in bug 315892, when you engaged in a very similar discussion there, the reason content assist appears when the file is seen as a JSP file and not as XHTML is your tag libraries are providing available attributes in TLDs for JSP, but they are not providing the same in *.taglib.xml files for Facelets. We can only provide XHTML tooling for third-party libraries based on the information provided by tag library developers. JSP and Facelets code paths are significantly different, even developed by separate teams. There's no simple "switch" that can be toggled to say "do JSP-style stuff for XHTML". Work needs to be done, and we are always willing to review contributions. Just because we provide functionality for facelets and JSF 2.0 that we don't offer for facelets and JSF 1.2 does not mean that we aren't supporting JEE 5. We attempt to support standards in the JSF Tools project, and facelets was not formally standardized until JEE 6. We support JEE5 and JEE 6 development. We can't possibly support every technology and library out there, but we try not to exclude their use. I don't think we are preventing the use of facelets with JSF 1.2 in any way, are we? I'm sorry that you feel like we offered something then took it away, but facelets support began life as an incubating sub-project because we knew we wanted to support facelets when it became standard and that we needed to begin work on it before JSF 2.0 was final. It was offered as a technology preview as we worked towards what we now have.
Hi Ian, I have written a blog how to configure a Maven based JEE Web Project to get the .xhtml content assist working in helios. Maybe this is usefull: http://workflow.imixs.org/roller/ralphsjavablog/entry/eclipse_helios_jsf_content_assist
What I am surprised to, is that this configuration works for all tags. The content assist recognizes from now on the RichFaces an a4j Tags as well and provides all help textes for attributes and tags. There is no need to tell eclipse anything about the RichFaces Library. It seems to me that this is read from eclipse directly from my project class path?
(In reply to comment #4) > eclipse anything about the RichFaces Library. It seems to me that this is read > from eclipse directly from my project class path? Yes, you have enabled WTP features (e.g. reading TLDs for tags used in JSPs) by installing the web facet. Installing the JSF 2.0 facet would also enable the features you want for facelets. I do realize that you are not using JSF 2.0, but my point is simple; installing facets enables new functionality. Unfortunately, there is currently no facelets support prior to JSF 2.0.
