blob: 8e5e1ad3eeaf54334db2a6b764bbded8baa4ce16 [file] [log] [blame]
<html><head><META http-equiv="Content-Type" content="text/html; charset=UTF-8"><link type="text/css" href="../../../default_style.css" rel="stylesheet"><link type="text/css" href="../../../webtools/wtp.css" rel="stylesheet"><title>the javaserver faces tools subproject</title></head><body><table border="0" cellpadding="2" cellspacing="5" width="100%"><tbody><tr><td align="left" width="60%"><font class="indextop">jsf</font><br><font class="indexsub">the javaserver faces tools subproject</font></td><td width="40%"><img src="../../../webtools/images/wtplogosmall.jpg" align="middle" height="129" hspace="50" width="207" alt="WTP Logo" usemap="logomap"><map id="logomap" name="logomap"><area coords="0,0,207,129" href="/webtools/" alt="WTP Home"></map></td></tr></tbody></table><table border="0" cellpadding="2" cellspacing="5" width="100%"><col width="16"><col width="*"><tbody><tr><td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b><font color="#ffffff" face="Arial,Helvetica">Design discussion meeting notes: 2006-02-17.</font></b></td></tr><tr><td align="right" valign="top">
&nbsp;
</td><td valign="top"><h4>Attendees</h4></td></tr><tr><td align="right" valign="top">
&nbsp;
</td><td valign="top"><ul>
<li>
From Oracle: Raghu Srinivasan, Gerry Kessler, Ian
Trimble, Justin Chen, Cameron Bateman
</li>
<li>
From IBM: David Williams, Amy Wu, Phillip Avery, Nitin
Dahyabhai
</li>
<li>From Sybase: Jean Choi</li>
</ul></td></tr><tr><td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b><font color="#ffffff" face="Arial,Helvetica">Talking points for the discussion</font></b></td></tr><tr><td align="right" valign="top">
&nbsp;
</td><td valign="top"><b>JSF JSP Editor</b></td></tr><tr><td align="right" valign="top">
&nbsp;
</td><td valign="top"><p>
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
<br>
<i>Reasons</i>
<ul>
<li>
better control over content assist (we saw the
modelQueryExtension and it may work, but we desire
more control over proposal creation)
</li>
<li>
could not determine a way to add our own hyperlink
detector
</li>
<li>
if we have our own editor and config, should we
create a new content type or use the JSF Fragment?
</li>
</ul>
</p></td></tr><tr><td align="right" valign="top">
&nbsp;
</td><td valign="top"><p>
<b>Extended Configurations</b>
<br>
-what are all of the possible provisional configs - will
they become API in 1.5?
</p></td></tr><tr><td align="right" valign="top">
&nbsp;
</td><td valign="top"><p>
<b>Content Assist</b>
<br>
- lots of comments in computeProposals like:
<br>
//
////////////////////////////////////////////////////////////////////////////
// ANOTHER WORKAROUND UNTIL PARTITIONING TAKES CARE OF THIS
<br>
-what is this about and will partition take care of this in
1.5???
</p></td></tr><tr><td align="right" valign="top">
&nbsp;
</td><td valign="top"><p>
<b>Hyperlink</b>
<br>
- plans for multi-link presenter? - suggestions on how to
deal with 2 or more possible links per detection?
</p></td></tr><tr><td align="right" valign="top">
&nbsp;
</td><td valign="top"><p>
<b>Quick Fix/Quick Assist</b>
<br>
- what plans does JSP have? - appears that there is no
QuickFix annotation presenter in SSE framework.
</p></td></tr><tr><td align="right" valign="top">
&nbsp;
</td><td valign="top"><p>
<b>Content Model API</b>
<br>
- any thoughts about opening it up?
</p></td></tr><tr><td align="right" valign="top">
&nbsp;
</td><td valign="top"><p>
<b>JSF EL Parser</b>
<br>
- guidance???
</p></td></tr><tr><td align="right" valign="top">
&nbsp;
</td><td valign="top"><p>SSE/JSP Plans for 1.5?</p></td></tr><tr><td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b><font color="#ffffff" face="Arial,Helvetica">Meeting Details</font></b></td></tr><tr><td align="right" valign="top">
&nbsp;
</td><td valign="top"><p>
Discussions were centered generally around usage of the
SSE/JSP frameworks with respect to a JSF JSP Source Page
Editor.
</p></td></tr><tr><td align="right" valign="top">
&nbsp;
</td><td valign="top"><ul>
<li>
there should be no new JSF configuration or JSF content
type. JSF project should use the JSP configuration and
use the avaiable extensions
</li>
<li>
content assist - use the modelQueryExtension to provide
attribute value proposals
</li>
<li>
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.
</li>
<li>
validation - JSF validators should use the
sourcevalidation extension point using jsp content type
on approriate partitions
</li>
<li>
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.
</li>
<li>
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
</li>
<li>
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.
</li>
</ul></td></tr><tr><td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b><font color="#ffffff" face="Arial,Helvetica">Issues</font></b></td></tr><tr><td align="right" valign="top">
&nbsp;
</td><td valign="top"><p></p></td></tr><tr><td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b><font color="#ffffff" face="Arial,Helvetica">Action Items</font></b></td></tr><tr><td align="right" valign="top">
&nbsp;
</td><td valign="top"><p>
Raghu to schedule next meeting in two weeks on 2006-03-03.
</p></td></tr></tbody></table></body></html>