| Milestone 1 Feature set + Next Status meeting [message #573576] |
Fri, 07 October 2005 19:07 |
 Raghu Srinivasan
Messages: 265
Registered: July 2009 |
Senior Member |
|
|
This is a multi-part message in MIME format.
--------------080201030705010809070805
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Hi,
The JSF Project has been provisioned! We now have CVS access, website
and a dev mailing list. We are fixing the website and will share all the
relevant information.
I have attached a doc that lists the proposed feature set for Milestone
1 of this project. The planned release date for this is around 12/16/05.
Please review and post your feedback to this newsgroup.
We will have the next status call on Tuesday instead of Monday to
accommodate the Canadian Holiday. I propose we meet at 2.00 PM PST.
Thanks
Raghu
Date:10/11/05
Time: 2.00 PM PDT
Conference Call info:
Call one of the MeetingPlace phone numbers:
From the AMER region dial:
1-888-967-2253
+1-650-607-2253
From the APAC region dial:
1800 222 712 (Australia toll-free)
+800 9491 2777
+61 2 8817 6100
From the EMEA region dial:
+44 118 924 9000
Meeting ID : 444461
Meeting Passcode : 573573
Conference Call info:
Call one of the MeetingPlace phone numbers:
From the AMER region dial:
1-888-967-2253
+1-650-607-2253
From the APAC region dial:
1800 222 712 (Australia toll-free)
+800 9491 2777
+61 2 8817 6100
From the EMEA region dial:
+44 118 924 9000
Meeting ID : 444461
Meeting Passcode : 573573
--------------080201030705010809070805
Content-Type: text/html; charset=UTF-8;
name="FeatureSpecs-M1.html"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename="FeatureSpecs-M1.html"
<html>
<head>
<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<link rel="stylesheet" href="../../default_style.css" type="text/css">
<link rel="stylesheet" href="../../webtools/wtp.css" type="text/css">
<title>JSF Tools Project Features for Milestone 1</title>
</head>
<body>
<table width="100%" cellspacing="5" cellpadding="2" border="0">
<col width="16">
<col width="*">
<tbody>
<tr>
<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Introduction</font></b></td>
</tr>
<tr>
<td valign="top" align="right"> </td><td valign="top">
<p>
This document defines the set of features that will be
delivered in the Milestone 1 of the project. This document
is a draft meant to solicit community feedback.
<b>
Please send all feedback to the
<a class="bodylink" href="news://news.eclipse.org/eclipse.webtools.jsf">
eclipse.webtools.jsf
</a>
newsgroup.
</b>
</p>
</td>
</tr>
<tr>
<td valign="top" align="right"> </td><td valign="top">
<p>
Following are the main themes for this milestone release:
<li>Define the JSF Facet</li>
<li>
Provide a first-class editor for the Application
Configuration resource file
</li>
<li>
Define the complete JSF Application model including all
the JSF specific artifacts.
</li>
</p>
</td>
</tr>
<tr>
<td valign="top" align="right"> </td><td valign="top">
<p>
The functionality delivered in this milestone will allow a
user to build a simple JSF application and execute it on the
target server. The following section gives an end user
perspective of the features by enumerating all the use cases
we plan to handle in this release. Given one of the main
goal of this project is to provide an extensible framework,
the section will also list use cases for the extensibility
that will be provided as part of this milestone.
</p>
</td>
</tr>
<tr>
<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">Use Cases</font></b></td>
</tr>
<tr>
<td valign="top" align="right"> </td><td valign="top">
<p>
<h4>1. Register the JSF Implementation.</h4>
The user experience will be similar to that of registering
the JRE. For each implementation registered, a user can
specify:
<ul>
<li>Name</li>
<li>JSF Version supported</li>
<li>Libraries</li>
<li>Tag libraries</li>
<li>Default servlet name</li>
<li>Default servlet class</li>
</ul>
A JSF implementation can be selected during project creation
or when adding JSF facets to an existing web project.
</p>
</td>
</tr>
<tr>
<td valign="top" align="right"> </td><td valign="top">
<p>
<h4>
2. Create a Dynamic Web Project with the JSF Project
Facet.
</h4>
<h4>
3. Add the JSF Project Facet to an existing Dynamic Web
Project.
</h4>
</p>
</td>
</tr>
<tr>
<td valign="top" align="right"> </td><td valign="top">
<p>
In both the scenarios, a user has the following options to
choose:
<ul>
<li>Select JSF implementation from registry</li>
<li>Select the JSF Version</li>
<li>
Create single application configuration resource
file
</li>
<ul>
<li>
Filename defaults to preference, overridable
Location defaults to ".../WEB-INF", allows
overridable
</li>
<li>
Updates context-param in web.xml if selected
location/filename is not
"WEB-INF/faces-config.xml"
</li>
</ul>
<li>
Update the web.xml with servlet and servlet-mapping
information
</li>
<ul>
<li>
Servlet name/classname default to preferences,
overridable
</li>
<li>
Servlet-mapping defaults to preference,
overridable
</li>
</ul>
</ul>
</p>
</td>
</tr>
<tr>
<td valign="top" align="right"> </td><td valign="top">
<p>
<h4>4. Create a JSF JSP Page.</h4>
This will be similar to the New JSP Wizard. The user can
specify the following.
<ul>
<li>Name</li>
<li>Location</li>
<li>JSF template (optional)</li>
</ul>
</p>
</td>
</tr>
<tr>
<td valign="top" align="right"> </td><td valign="top">
<p>
<h4>5. Create Application Configuration Resource file.</h4>
User can specify the following.
<ul>
<li>
File Name, defaults to the name specified in the
preference
</li>
<li>
Location, defaults to the path specified in the
preference
</li>
</ul>
</p>
</td>
</tr>
<tr>
<td valign="top" align="right"> </td><td valign="top">
<p>
<h4>6. Edit the Application Configuration Resource file.</h4>
For this milestone, the Editor will be a basic SSE based XML
Source Editor with the following features.
<ul>
<li>JSF-specific content assist</li>
<li>
"Hot linking" (ctrl-click) for classes to their
corresponding java file. If the class doesn't exist,
the editor will provide option to launch wizard to
create it
</li>
</ul>
</p>
</td>
</tr>
<tr>
<td valign="top" align="right"> </td><td valign="top">
<p>
<h4>
7. Run/ Debug a JSF JSP Page (and Application
Configuration file) on the Server.
</h4>
</p>
</td>
</tr>
<tr>
<td valign="top" align="right"> </td><td valign="top">
<p>
<h4>
8. User will be able to specify the following
preferences.
</h4>
<ul>
<li>Default JSF implementation</li>
<li>Default JSF Version</li>
<li>
Default FileName of the Application Configuration
Resource file.
</li>
<li>
Default location of the Application Configuration
Resource file.
</li>
<li>Default JSF Template</li>
</ul>
</p>
</td>
</tr>
<tr>
<td valign="top" align="right"> </td><td valign="top">
<p>
<h4>9. Extensions</h4>
<ul>
<li>API to register a JSF implementation</li>
<li>
API to add the JSF Project Facet to a Dynamic Web
Project
</li>
<li>
API to create an Application Configuration Resource
file.
</li>
<li>
API to add instances of various artifacts of the
Application Configuration Resource file such as the
Managed bean, Navigation Rule, Validator etc.
</li>
<li>
Extension points for the Application Configuration
Editor
</li>
</ul>
</p>
</td>
</tr>
</tbody>
</table>
</body>
</html>
--------------080201030705010809070805--
Raghu Srinivasan,
Project Lead - JSF
|
|
|
Powered by
FUDForum. Page generated in 0.03532 seconds
] 
Search
Help
Register
Login
Home
