RE: [wtp-jsf-dev] Facelets TagLib Support

["Oakes, Donald" <Donald.Oakes@xxxxxxxxx>]

Cameron,

Thanks very much for your response.  To get a feel for the complexity
involved in adding Facelets support I've hacked some additional logic
into TLDCMDocumentManager to handle parsing of Facelets taglib
declarations.

With this in place I was able to replicate the functionality outlined in
the tutorial at:

http://www.eclipse.org/webtools/jsf/dev_resource/JSFTutorial-RC3/JSFTool
s_tutorial.html

(including EL content assist for tag-contributed variables).

I also had to associate xhtml files with the JSP content type in my
preferences and add the HTML_DEFAULT partition type to the
editorConfiguration extension in the jsf.ui plugin.xml.

This is all just hacking, of course, but it gives me a feel for what
needs to be done.

I will begin some preliminary work on an org.eclipse.jst.jsf.facelets
plugin.  I don't have a great deal of free time to contribute, but I
think it's important that Facelets support be added to Eclipse, so as
not to fall too far behind NetBeans in this area
(http://wiki.netbeans.org/wiki/view/FaceletsSupport).

Thanks again for your advice.  Please let me know if you have additional
thoughts.

 - Don


-----Original Message-----
From: wtp-jsf-dev-bounces@xxxxxxxxxxx
[mailto:wtp-jsf-dev-bounces@xxxxxxxxxxx] On Behalf Of Cameron Bateman
Sent: Monday, December 04, 2006 3:41 PM
To: Java Server Faces Tools developer discussion
Subject: Re: [wtp-jsf-dev] Facelets TagLib Support

Hi Donald,

We can certainly look into moving more of our EL validation toward API.

I'm not yet conversant enough in the details of facelet to  know what 
hidden obstacles there may be.  For example, the EL validation is as 
generic as we could make it, but underlying the current implementation 
is the "JSPModelProcessor".  This is used to process the JSP file itself

for tag-contributed variable and uses meta-data to determine what tags 
contribute variables.  I don't know how well this will work with 
Facelets, although we can certainly look at it.

The main wtp-dev mailing list is better for questions about JST taglib 
support.  They have told us that they are short of resources on this 
cycle,  but they are open to idea of patches, so that might be a good 
way to introduce the changes you need without creating a lot of 
redundant code.


--Cam

Oakes, Donald wrote:

> Hello,
>
>  
>
> I have been looking at the refactored JSF Plug-In code with a view 
> toward contributing Facelets support.  The Expression Language 
> validation seems to have been genericized to the point where it will 
> work with facelets as well as JSPs.  However, with the validation 
> being performed in JSPSemanticsValidator I have to associate facelets 
> .xhtml files with JSP content type to take advantage this.  Is it 
> possible that the functionality in checkIfELAndValidate() could be 
> exposed for other content types aside from JSPs?
>
>  
>
> It appears that taglib support for facelets is going to be a lot more 
> complicated due to the fact that much of the JST taglib processing is 
> JSP-centric.  Facelets JSF tags can be processed very similarly to JSP

> JSF tags, with only the taglib declaration having a slightly different

> syntax (xmlns versus taglib).  Obviously I would like to reuse as much

> as possible.  Can anyone offer me any advice?  Has there been any 
> discussion with the jst.jsp developers regarding potential refactoring

> to accommodate other doctypes beyond JSPs?  I could provide parallel 
> implementations in an org.eclipse.jst.facelets plugin, but it seems 
> that this would result in way too much overlap.
>
>  
>
> Any advice will be greatly appreciated.
>
>  
>
> Thanks and Regards,
>
>  - Don Oakes
>
>
>
> This communication is the property of Qwest and may contain 
> confidential or privileged information. Unauthorized use of this 
> communication is strictly prohibited and may be unlawful. If you have 
> received this communication in error, please immediately notify the 
> sender by reply e-mail and destroy all copies of the communication and

> any attachments.
>
>-----------------------------------------------------------------------
-
>
>_______________________________________________
>wtp-jsf-dev mailing list
>wtp-jsf-dev@xxxxxxxxxxx
>https://dev.eclipse.org/mailman/listinfo/wtp-jsf-dev
>  
>

_______________________________________________
wtp-jsf-dev mailing list
wtp-jsf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-jsf-dev