Attendees

• From Oracle: Raghu Srinivasan, Gerry Kessler, Ian Trimble, Justin Chen, Cameron Bateman
• From IBM: David Williams, Amy Wu, Phillip Avery, Nitin Dahyabhai
• From Sybase: Jean Choi

We have decided for now to go ahead and create our own editor with our own config rather than request enhancements to the JSP config to support our requirements
Reasons

• better control over content assist (we saw the modelQueryExtension and it may work, but we desire more control over proposal creation)
• could not determine a way to add our own hyperlink detector
• if we have our own editor and config, should we create a new content type or use the JSF Fragment?

Extended Configurations
-what are all of the possible provisional configs - will they become API in 1.5?

Content Assist
- lots of comments in computeProposals like:
// //////////////////////////////////////////////////////////////////////////// // ANOTHER WORKAROUND UNTIL PARTITIONING TAKES CARE OF THIS
-what is this about and will partition take care of this in 1.5???

Hyperlink
- plans for multi-link presenter? - suggestions on how to deal with 2 or more possible links per detection?

Quick Fix/Quick Assist
- what plans does JSP have? - appears that there is no QuickFix annotation presenter in SSE framework.

Content Model API
- any thoughts about opening it up?

JSF EL Parser
- guidance???

SSE/JSP Plans for 1.5?

Discussions were centered generally around usage of the SSE/JSP frameworks with respect to a JSF JSP Source Page Editor.

• there should be no new JSF configuration or JSF content type. JSF project should use the JSP configuration and use the avaiable extensions
• content assist - use the modelQueryExtension to provide attribute value proposals
• hyperlink detection - SSE team is waiting on https://bugs.eclipse.org/bugs/show_bug.cgi?id=88293 to provide support for extensions. The JSF team may need to postpone this feature or provide an interim solution.
• validation - JSF validators should use the sourcevalidation extension point using jsp content type on approriate partitions
• JSF EL - JSF team to implement a parser using JFlex preferably. BEA supplied the current JSP parser. SSE team indicated that some aspects may be tricky.
• Annotations Registry - JSF team has prototyped a registry of annotations to content models external from the content model itself. JSF project will be using the meta-data it provides on attributes and elements to provide meta-data driven features like content assist and validation. SSE team has had requests for something similar. https://bugs.eclipse.org/bugs/show_bug.cgi?id=122909 . JSF Team will publish it's feature spec shortly for comment and perform a demonstration in a couple of weeks
• Enhancements to SSE/JSP - If there are bugs or enhacements to the SSE/JSP layer, don't be afraid to fix small issues with patches. larger issues see if we can fix and contribute ourselves. Communicate.

Raghu to schedule next meeting in two weeks on 2006-03-03.