1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
|
<html>
<head>
<title>Proposal for JSP 2.0 Expression Language Interpreter Package</title>
</head>
<body bgcolor="white">
<div align="center">
<h1>Proposal for <em>JSP 2.0 Expression Language Interpreter</em> Package</h1>
</div>
<h3>(0) Rationale</h3>
<p>The JSP Standard Tag Library (JSTL), version 1.0, introduced the
concept of an Expression Language (EL), whose main goal is to provide
page authors with an easy way to access and manipulate application
data without requiring the use of scriptlets
<p>JSP 2.0 adopted the EL specification from JSTL, and expanded its
scope: EL expressions are no longer limited to JSTL action attributes,
but may be used in any standard or custom action attribute declared to
accept a runtime expression. In addition, EL expressions may now also
be used directly in template text outside of any actions. JSP 2.0 also
added an important feature to the EL specification: EL functions,
which allow page authors to invoke static methods in Java classes from
EL expressions. Additionally, JSP 2.0 allows programmatic access and
customization of the EL evaluator through a set of standard interfaces
and abstract classes.
<p>Currently, there are a number of projects (including Tomcat 5 and Java
Server Faces) that leverage the EL implementation of the Standard
Taglib. In addition, there seems to be interest in leveraging the EL
in the context of scripting workflow activities using custom tag
libraries.
<p>In order to make the EL implementation available to Tomcat 5, the
Tomcat team defined a new "ant" target for the Standard Taglib that
builds just the EL portion and packages it in a JAR file
("jsp20el.jar") which is stored in Tomcat's common/lib
directory. This approach has always been considered an interim
solution only, until the EL implementation would move from the
Standard Taglib to a more visible location such as jakarta-commons.
<h3>(1) Scope of the package</h3>
The package shall provide an implementation of the Expression Language
specification which is part of the JSP 2.0 standard.
<h3>(1.5) Interaction with other packages</h3>
The package shall provide an implementation of the standard interfaces
and abstract classes of the javax.servlet.jsp.el package, which is
defined in the JSP 2.0 specification.
<h3>(2) Identify the initial source for the package</h3>
The initial codebase will be taken from the Standard Taglib project
hosted at jakarta-taglibs. The source of the Standard Taglib is
available as part of the <a href="http://jakarta.apache.org/builds/jakarta-taglibs/nightly/src/">jakarta-taglibs nightly source distribution</a>.
<h3>(2.1) Identify the base name for the package</h3>
The base name of the package shall be org.apache.commons.el
<h3>(2.2) Identify the coding conventions for this package</h3>
The package follows <a href="http://java.sun.com/docs/codeconv/html/CodeConvTOC.doc.html">Sun's Java coding conventions</a>.
<h3>(3) Identify any Jakarta-Commons resources to be created</h3>
<h3>(3.1) Mailing list</h3>
The package shall use the jakarta-commons mailing list.
<h3>(3.2) CVS repositories</h3>
The package shall use a root branch of the jakarta-commons CVS.
<h3>(3.3) Bugzilla</h3>
The package shall be listed as the "EL" component under the "Commons"
project in Bugzilla.
<h3>(3.4) Jyve FAQ (when available)</h3>
n/a
<h3>(4) Initial Committers</h3>
<ul>
<li>Shawn Bayern</li>
<li>Nathan Abramson</li>
<li>Pierre Delisle</li>
<li>Hans Bergsten</li>
<li>Justyna Horwat</li>
<li>Craig R. McClanahan</li>
<li>Jan Luehe</li>
</ul>
</body>
</html>
|
