Return-Path: Delivered-To: apmail-jakarta-site-cvs-archive@www.apache.org Received: (qmail 49154 invoked from network); 18 Feb 2006 14:25:55 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 18 Feb 2006 14:25:55 -0000 Received: (qmail 40052 invoked by uid 500); 18 Feb 2006 14:25:54 -0000 Delivered-To: apmail-jakarta-site-cvs-archive@jakarta.apache.org Received: (qmail 39949 invoked by uid 500); 18 Feb 2006 14:25:54 -0000 Mailing-List: contact site-cvs-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Jakarta WebSite CVS List" Reply-To: "Jakarta General List" Delivered-To: mailing list site-cvs@jakarta.apache.org Received: (qmail 39938 invoked by uid 99); 18 Feb 2006 14:25:54 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 18 Feb 2006 06:25:54 -0800 X-ASF-Spam-Status: No, hits=-9.4 required=10.0 tests=ALL_TRUSTED,NO_REAL_NAME X-Spam-Check-By: apache.org Received: from [209.237.227.194] (HELO minotaur.apache.org) (209.237.227.194) by apache.org (qpsmtpd/0.29) with SMTP; Sat, 18 Feb 2006 06:25:52 -0800 Received: (qmail 49051 invoked by uid 65534); 18 Feb 2006 14:25:32 -0000 Message-ID: <20060218142532.49050.qmail@minotaur.apache.org> Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r378725 - /jakarta/site/docs/site/news/news-2006-q1.html Date: Sat, 18 Feb 2006 14:25:32 -0000 To: site-cvs@jakarta.apache.org From: rdonkin@apache.org X-Mailer: svnmailer-1.0.6 X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Author: rdonkin Date: Sat Feb 18 06:25:31 2006 New Revision: 378725 URL: http://svn.apache.org/viewcvs?rev=378725&view=rev Log: Problems with line endings after regenerating site. AFAIK no content change. The eol-style is now set to native. Modified: jakarta/site/docs/site/news/news-2006-q1.html (contents, props changed) Modified: jakarta/site/docs/site/news/news-2006-q1.html URL: http://svn.apache.org/viewcvs/jakarta/site/docs/site/news/news-2006-q1.html?rev=378725&r1=378724&r2=378725&view=diff ============================================================================== --- jakarta/site/docs/site/news/news-2006-q1.html (original) +++ jakarta/site/docs/site/news/news-2006-q1.html Sat Feb 18 06:25:31 2006 @@ -1,411 +1,411 @@ - - - - -The Jakarta Site - News and Status - 2006 Jan-Mar - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-

-Support -

- -

-Subprojects -

- -

-Incubating -

- -

-Ex-Jakarta -

- -
-
- -

-

- -

29 January 2006 - HiveMind 1.1.1 released

-
-

- HiveMind release 1.1.1 is now - available; this is a bug fix release. This release addresses performance bottlenecks - in HiveMind related to the use of unqualified class names, and the use of the threaded - and pooled service lifecycle models. HiveMind 1.1.1 is a drop-in replacement for - HiveMind 1.1, and is recommended for use with Tapestry 4.0 applications.

-

- Download - HiveMind -

-
- -

07 January 2006 - Tapestry 4.0 (final) released

-
-

After nearly two years of work, the Tapestry development team is proud to announce - the next major release of the Tapestry - web application framework.

-

Tapestry is an open-source framework for creating dynamic, robust, highly scalable - web applications in Java. Tapestry complements and builds upon the standard Java - Servlet API, and so it works in any servlet container or application server.

-

Tapestry divides a web application into a set of pages, each constructed from - components. This provides a consistent structure, allowing the Tapestry framework to - assume responsibility for key concerns such as URL construction and dispatch, - persistent state storage on the client or on the server, user input validation, - localization/internationalization, and exception reporting. Developing Tapestry - applications involves creating HTML templates using plain HTML, and combining the - templates with small amounts of Java code using (optional) XML descriptor files. In - Tapestry, you create your application in terms of objects, and the methods and - properties of those objects -- and specifically not in terms of URLs and query - parameters. Tapestry brings true object oriented development to Java web - applications.

-

Tapestry is specifically designed to make creating new components very easy, as this - is a routine approach when building applications. The distribution includes over - fifty components, ranging from simple output components all the way up to complex - data grids and tree navigators.

-

Tapestry is architected to scale from tiny applications all the way up to massive - applications consisting of hundreds of individual pages, developed by large, diverse - teams. Tapestry easily integrates with any kind of backend, including J2EE, HiveMind and Spring.

-

Tapestry 4.0 represents a significant advance over Tapestry 3.0. The following are - the most significant changes between the two releases:

-
    -
  • The new 4.0 specification DTDs have been simplified.
  • -
  • The syntax used for binding parameters inside an HTML template and inside an - XML specification is now consistent. Both make use of binding prefixes.
  • -
  • "Friendly" URLs (that is, URLs that pack more information into the path and - less into query parameters) are built in. This makes it easy to divide your - application across many folders (reducing clutter), and leverage J2EE - declarative security along the way.
  • -
  • Listener methods are much easier and more flexible; listener parameters in the - URL are automatically mapped to listener method parameters, and listener methods - can return the page name or page instance to activate.
  • -
  • Component parameters now just work, without having to worry about - "direction".
  • -
  • Applications can now have a global message catalog, in addition to per-page and - per-component message catalogs. Messages not found in the component message - catalog are searched for in the application catalog.
  • -
  • Full, native support for developing JSR-168 Portlets has been - added.
  • -
  • Tapestry 4.0 makes much less use of reflection and OGNL than Tapestry 3.0; partly because there - are many new binding prefixes and largely because of how parameters are now - implemented.
  • -
  • - HiveMind services and Spring beans can be directly injected - into page and component classes.
  • -
  • Tapestry 4.0 includes optional JDK 1.5 annotation support (but Tapestry still - works with JDK 1.3).
  • -
  • Tapestry 4.0 debuts a new and much more sophisticated user input validation - subsystem.
  • -
  • Line precise error reporting can now display the contents of files containing - errors.
  • -
  • Forms can now be canceled, bypassing client-side validation logic, and invoking - an alternate listener on the server-side.
  • -
  • You are no longer limited to just Global and Visit; you can have as many - application state objects as you like.
  • -
  • The use of HiveMind under the covers means that Tapestry can be easily - customized to fit your needs.
  • -
  • Page properties can now be persisted on the client, as well as in the session.
  • -
  • Components and component parameters can now be marked as deprecated. Component - parameters may have aliases (used when renaming a parameter).
  • -
  • The examples have been rewritten to take full advantage of Tapestry 4.0 - features, including annotations.
  • -
-

Tapestry is released under the Apache Software Licence 2.0.

-

Tapestry is distributed as a combined binary/source distribution, and an additional - documentation distribution. Tapestry may be downloaded from the Apache - Mirrors.

-

[ News Headlines index - ]

-

[ Newsletters - Archive ]

-

[ Jakarta Product News - from 2006 Jan-Mar ]

-

[ Jakarta Product News - from 2005 Oct-Dec ]

-

[ Jakarta Product News - from 2005 Jul-Sep ]

-

[ Jakarta Product News from - 2005 Apr-Jun ]

-

[ Jakarta Product News from - 2005 Jan-Mar ]

-

[ Jakarta Product News - from 2004 Jul-Dec ]

-

[ Jakarta Product News - from 2004 Jan-Jun ]

-

[ Other News from - 2004 Jul-Dec ]

-

[ Other News from - 2004 Jan-Jun ]

-

[ Jakarta News from 2003 ]

-

[ Other News from 2003 - ]

-

[ Jakarta News from 2002 ]

-

[ Other News from 2002 - ]

-

[ News from 2001 ]

-

[ News from 2000 ]

-
-

-
-
-

-About Jakarta -

- -

-Reference -

- -

-Search Jakarta -

- -

-Unaffiliated Links -

- -

-Unaffiliated Translations -

- -
-
-
- -
- - + + + + +The Jakarta Site - News and Status - 2006 Jan-Mar + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+Support +

+ +

+Subprojects +

+ +

+Incubating +

+ +

+Ex-Jakarta +

+ +
+
+ +

+

+ +

29 January 2006 - HiveMind 1.1.1 released

+
+

+ HiveMind release 1.1.1 is now + available; this is a bug fix release. This release addresses performance bottlenecks + in HiveMind related to the use of unqualified class names, and the use of the threaded + and pooled service lifecycle models. HiveMind 1.1.1 is a drop-in replacement for + HiveMind 1.1, and is recommended for use with Tapestry 4.0 applications.

+

+ Download + HiveMind +

+
+ +

07 January 2006 - Tapestry 4.0 (final) released

+
+

After nearly two years of work, the Tapestry development team is proud to announce + the next major release of the Tapestry + web application framework.

+

Tapestry is an open-source framework for creating dynamic, robust, highly scalable + web applications in Java. Tapestry complements and builds upon the standard Java + Servlet API, and so it works in any servlet container or application server.

+

Tapestry divides a web application into a set of pages, each constructed from + components. This provides a consistent structure, allowing the Tapestry framework to + assume responsibility for key concerns such as URL construction and dispatch, + persistent state storage on the client or on the server, user input validation, + localization/internationalization, and exception reporting. Developing Tapestry + applications involves creating HTML templates using plain HTML, and combining the + templates with small amounts of Java code using (optional) XML descriptor files. In + Tapestry, you create your application in terms of objects, and the methods and + properties of those objects -- and specifically not in terms of URLs and query + parameters. Tapestry brings true object oriented development to Java web + applications.

+

Tapestry is specifically designed to make creating new components very easy, as this + is a routine approach when building applications. The distribution includes over + fifty components, ranging from simple output components all the way up to complex + data grids and tree navigators.

+

Tapestry is architected to scale from tiny applications all the way up to massive + applications consisting of hundreds of individual pages, developed by large, diverse + teams. Tapestry easily integrates with any kind of backend, including J2EE, HiveMind and Spring.

+

Tapestry 4.0 represents a significant advance over Tapestry 3.0. The following are + the most significant changes between the two releases:

+
    +
  • The new 4.0 specification DTDs have been simplified.
  • +
  • The syntax used for binding parameters inside an HTML template and inside an + XML specification is now consistent. Both make use of binding prefixes.
  • +
  • "Friendly" URLs (that is, URLs that pack more information into the path and + less into query parameters) are built in. This makes it easy to divide your + application across many folders (reducing clutter), and leverage J2EE + declarative security along the way.
  • +
  • Listener methods are much easier and more flexible; listener parameters in the + URL are automatically mapped to listener method parameters, and listener methods + can return the page name or page instance to activate.
  • +
  • Component parameters now just work, without having to worry about + "direction".
  • +
  • Applications can now have a global message catalog, in addition to per-page and + per-component message catalogs. Messages not found in the component message + catalog are searched for in the application catalog.
  • +
  • Full, native support for developing JSR-168 Portlets has been + added.
  • +
  • Tapestry 4.0 makes much less use of reflection and OGNL than Tapestry 3.0; partly because there + are many new binding prefixes and largely because of how parameters are now + implemented.
  • +
  • + HiveMind services and Spring beans can be directly injected + into page and component classes.
  • +
  • Tapestry 4.0 includes optional JDK 1.5 annotation support (but Tapestry still + works with JDK 1.3).
  • +
  • Tapestry 4.0 debuts a new and much more sophisticated user input validation + subsystem.
  • +
  • Line precise error reporting can now display the contents of files containing + errors.
  • +
  • Forms can now be canceled, bypassing client-side validation logic, and invoking + an alternate listener on the server-side.
  • +
  • You are no longer limited to just Global and Visit; you can have as many + application state objects as you like.
  • +
  • The use of HiveMind under the covers means that Tapestry can be easily + customized to fit your needs.
  • +
  • Page properties can now be persisted on the client, as well as in the session.
  • +
  • Components and component parameters can now be marked as deprecated. Component + parameters may have aliases (used when renaming a parameter).
  • +
  • The examples have been rewritten to take full advantage of Tapestry 4.0 + features, including annotations.
  • +
+

Tapestry is released under the Apache Software Licence 2.0.

+

Tapestry is distributed as a combined binary/source distribution, and an additional + documentation distribution. Tapestry may be downloaded from the Apache + Mirrors.

+

[ News Headlines index + ]

+

[ Newsletters + Archive ]

+

[ Jakarta Product News + from 2006 Jan-Mar ]

+

[ Jakarta Product News + from 2005 Oct-Dec ]

+

[ Jakarta Product News + from 2005 Jul-Sep ]

+

[ Jakarta Product News from + 2005 Apr-Jun ]

+

[ Jakarta Product News from + 2005 Jan-Mar ]

+

[ Jakarta Product News + from 2004 Jul-Dec ]

+

[ Jakarta Product News + from 2004 Jan-Jun ]

+

[ Other News from + 2004 Jul-Dec ]

+

[ Other News from + 2004 Jan-Jun ]

+

[ Jakarta News from 2003 ]

+

[ Other News from 2003 + ]

+

[ Jakarta News from 2002 ]

+

[ Other News from 2002 + ]

+

[ News from 2001 ]

+

[ News from 2000 ]

+
+

+
+
+

+About Jakarta +

+ +

+Reference +

+ +

+Search Jakarta +

+ +

+Unaffiliated Links +

+ +

+Unaffiliated Translations +

+ +
+
+
+ +
+ + Propchange: jakarta/site/docs/site/news/news-2006-q1.html ------------------------------------------------------------------------------ svn:eol-style = native --------------------------------------------------------------------- To unsubscribe, e-mail: site-cvs-unsubscribe@jakarta.apache.org For additional commands, e-mail: site-cvs-help@jakarta.apache.org