| <?xml version="1.0" encoding="UTF-8"?> |
| <?xml-stylesheet type="text/xsl" href="../../wtp.xsl"?> |
| <html> |
| <head> |
| <meta name="root" content="../../.." /> |
| <title>the javaserver faces tools subproject</title> |
| </head> |
| <body> |
| |
| <h1>jsf</h1> |
| <h2>Design discussion meeting notes: 2006-02-17.</h2> |
| <h4>Attendees</h4> |
| <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> |
| |
| <h2>Talking points for the discussion</h2> |
| |
| <b>JSF JSP Editor</b> |
| <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></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> |
| <p> |
| <b>Extended Configurations</b> |
| <br></br> |
| -what are all of the possible provisional configs - will |
| they become API in 1.5? |
| </p> |
| <p> |
| <b>Content Assist</b> |
| <br></br> |
| - lots of comments in computeProposals like: |
| <br></br> |
| // |
| //////////////////////////////////////////////////////////////////////////// |
| // ANOTHER WORKAROUND UNTIL PARTITIONING TAKES CARE OF THIS |
| <br></br> |
| -what is this about and will partition take care of this in |
| 1.5??? |
| </p> |
| <p> |
| <b>Hyperlink</b> |
| <br></br> |
| - plans for multi-link presenter? - suggestions on how to |
| deal with 2 or more possible links per detection? |
| </p> |
| <p> |
| <b>Quick Fix/Quick Assist</b> |
| <br></br> |
| - what plans does JSP have? - appears that there is no |
| QuickFix annotation presenter in SSE framework. |
| </p> |
| <p> |
| <b>Content Model API</b> |
| <br></br> |
| - any thoughts about opening it up? |
| </p> |
| <p> |
| <b>JSF EL Parser</b> |
| <br></br> |
| - guidance??? |
| </p> |
| <p>SSE/JSP Plans for 1.5?</p> |
| <h2>Meeting Details</h2> |
| <p> |
| Discussions were centered generally around usage of the |
| SSE/JSP frameworks with respect to a JSF JSP Source Page |
| Editor. |
| </p> |
| <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> |
| <h2>Issues</h2> |
| <p></p> |
| <h2>Action Items</h2> |
| <p> |
| Raghu to schedule next meeting in two weeks on 2006-03-03. |
| </p> |
| |
| |
| </body> |
| </html> |