Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[wtp-dev] JSF Page Editing

David et al,

 

The JSF Tooling Team is starting to take a closer look at how we will be providing enhancements to the JSP Structured Editor and we have a whole bunch of questions.  

 

Some of the enhancements that we are considering:

 

    - JSF EL support

    - content assist/Quick Fix create for managed beans

    - hyperlink to managed beans

 

Taking a(n incomplete) look at the SSE architecture, it leads me to think that the way we should implement is to (minimally) provide our own SourceViewerConfiguration via the org.eclipse.wst.sse.ui.editorConfiguration ext-pt.   I am thinking our StructuredContentViewer would subclass the StructuredTextViewerConfigurationJSP as is suggested by "webtools\wst\components\sse\designs\EditorConfiguration.html".     

 

However, what I am stuck on is that there appears not to be a new target content type.  A JSF page is just a JSP page and a user would expect to be able to use .jsp file extensionsDoes the file extension determine which editor configuration that will get used?   If the user opens a JSP file and added JSF content (jsf taglib imports and jsf elements), can the configuration suddenly switch to use JSF?   

 

Undoubtedly the SSE/JSP team has thought a little about support for JSF and I was looking for advice on what would be the best way to progress.   Would it be better if we provided enhancements directly to the JSP editor?  

 

Hopefully these aren't totally stupid questions.   Any pointers you can provide would be great and if you would prefer to take this off-line, that is fine too.

 

Thanks,

Gerry Kessler   

WTP JSF Tools Team

 


Back to the top