hlship 2005/06/24 13:09:26
Modified: . version.properties
src/documentation/content/xdocs index.xml
Log:
Add link back to 3.0.3 documentation.
Revision Changes Path
1.11 +1 -1 jakarta-tapestry/version.properties
Index: version.properties
===================================================================
RCS file: /home/cvs/jakarta-tapestry/version.properties,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- version.properties 24 Jun 2005 18:22:55 -0000 1.10
+++ version.properties 24 Jun 2005 20:09:26 -0000 1.11
@@ -12,4 +12,4 @@
# See the License for the specific language governing permissions and
# limitations under the License.
-project.version=4.0-beta-1
+project.version=4.0-beta-2-snapshot
1.16 +3 -2
jakarta-tapestry/src/documentation/content/xdocs/index.xml
Index: index.xml
===================================================================
RCS file:
/home/cvs/jakarta-tapestry/src/documentation/content/xdocs/index.xml,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- index.xml 23 Jun 2005 20:12:16 -0000 1.15
+++ index.xml 24 Jun 2005 20:09:26 -0000 1.16
@@ -182,7 +182,8 @@
<p>
Tapestry 4.0 should be production-ready soon. It needs more exposure and
more documentation. For the
-momement, it is still recommended that you stick with Tapestry
<strong>3.0.3</strong>,
+momement, it is still recommended that you stick with Tapestry
+ <a
href="http://jakarta.apache.org/tapestry/3.0.3/";><strong>3.0.3</strong></a>,
the latest stable release.
</p>
@@ -191,7 +192,7 @@
This feature allows you to define a default binding prefix for a parameter
as part of the <parameter>
element. Then in your template, you can omit the prefix ... this allows you
to say
<code>value="userId"</code> rather than <code>value="ognl:userId"</code>,
-or <code>listener="doSubmit"</code> rather than
<code>value="listener:doSubmit"</code>.
+or <code>listener="doSubmit"</code> rather than
<code>listener="listener:doSubmit"</code>.
The pros and cons are still being evaluated and exposure of the beta release
may provoke a new discussion
and possibly the removal of this feature. If you are intending to start work
on a production application
using Tapestry 4.0, you are advised to <em>always</em> use an explicit
binding prefix.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
