[CONF] Apache Tapestry > Release Notes 5.2
Bob Harner edited the page: Release Notes 5.2 Comment: fixed language param of code macro ... This is the consolidated list of changes between Tapestry versions 5.1 and 5.2. To upgrade from 5.1 to 5.2, most users will be able to just update the Maven dependency in their POM file (or download the new JAR file) and the new version will just work. However, please read carefully below before upgrading, and also review the How to Upgrade instructions. Contents Table of Contents maxLevel 2 minLevel 2 Breaking Changes The following changes have been made in Tapestry 5.2 that are likely to result in unexpected behavior if your application relies on the changed functionality. Please review this list carefully before upgrading from 5.1 to 5.2. Also check the Deprecated API List for non-breaking changes. Page classes with instance variables that are not thread safe must be created in a method rather than declared as an instance variable. For example, creating an instance variable private final DateFormat format = DateFormat.getDateInstance(DateFormat.MEDIUM, locale); in a page and using it will cause problems because DateFormat is not thread safe. Instead, you must create the DateFormat in a method. See Release Notes: Tapestry 5.2.0 (below) for details. Link.toAbsoluteURI() now returns the absolute URL, which includes the scheme, hostname and possibly port (e.g., "http://example.com:8080/myapp/viewproduct/4"), rather than a relative URL (e.g., "/myapp/viewproduct/4"). See Release Notes: Tapestry 5.2.2 (below) for details. The Label component no longer outputs an id: Previously val
[CONF] Apache Tapestry > Release Notes
Release Notes Page edited by Massimo Lusetti Changes (2) ... ||Release || Release Notes || Status || Released | | Tapestry 5.4 | [Release Notes for 5.4|Release Notes 5.4] | *Under Development* | | | Tapestry 5.3.7 | [Release Notes for 5.3.7|Release Notes 5.3.7] | *Currently under vote* *Current Stable Release* | 24 Apr 2013 | | Tapestry 5.3.6 | [Release Notes for 5.3.6|Release Notes 5.3.6] | *Current Stable Release* | 12 Oct 2012 | | Tapestry 5.3.5 | [Release Notes for 5.3.5|Release Notes 5.3.5] | | 29 Aug 2012 | | Tapestry 5.3.4 | [Release Notes for 5.3.4|Release Notes 5.3.4] | | 16 Jul 2012 | | Tapestry 5.3.3 | [Release Notes for 5.3.3|Release Notes 5.3.3] | | 24 Apr 2012 | ... Full Content These release notes describe the changes in each Tapestry version. Be sure to read How to Upgrade too. Release Release Notes Status Released Tapestry 5.4 Release Notes for 5.4 Under Development Tapestry 5.3.7 Release Notes for 5.3.7 Current Stable Release 24 Apr 2013 Tapestry 5.3.6 Release Notes for 5.3.6 12 Oct 2012 Tapestry 5.3.5 Release Notes for 5.3.5 29 Aug 2012 Tapestry 5.3.4 Release Notes for 5.3.4 16 Jul 2012 Tapestry 5.3.3 Release Notes for 5.3.3 24 Apr 2012 Tapestry 5.3.2 Release Notes for 5.3.2 07 Feb 2012 Tapestry 5.3.1 Release Notes for 5.3.1 21 Dec 2011 Tapestry 5.3 Release Notes for 5.3 21 Nov 2011 Tapestry 5.2.6 Release Notes for 5.2.x 22 Jun 2011 Tapestry 5.1 Release Notes for 5.1.x 12 Apr 2009 Tapestry 5.0 Release Notes for 5.0.x Dec 2008 Change Notification Preferences View Online | View Changes
[CONF] Apache Tapestry > Release Notes 5.3.7
Release Notes 5.3.7 Page added by Massimo Lusetti Release Notes This is the consolidated list of changes between Tapestry versions 5.3.6 and 5.3.7. Tapestry 5.3.7 is a drop-in replacement for prior Tapestry 5.3 releases. To upgrade, just update the Maven dependency in your POM file (or download the new JAR file) and the new version will just work. However, please review the How to Upgrade instructions before upgrading. This is a bug fix release, mainly focused on three aspects: make Tapestry work better under Tomcat minimize the possibility of clash for generated ids let the BeanEditor be more JSR-303 friendly Some work has been made on the form component too. As with any Tapestry upgrade, be sure to change yourapplication's version number. Release Notes - Tapestry 5 - Version 5.3.7 Bug [TAP5-1010] - Fix Finnish validation message translation - corrected file attached [TAP5-1890] - PlaceholderBlock should implement RenderCommand [TAP5-1995] - Tapestry5 Application can not be deployed as Tomcat7 HotDeploy Package [TAP5-2015] - Tomcat .war path is not decoded properly [TAP5-2025] - Duplicate generated ids [TAP5-2041] - Links within subheadings are invisible on Javadoc pages [TAP5-2084] - Form should decode its link parameters [TAP5-2101] - BeanEditor should always provide a new BeanValidationContext (JSR-303) Improvement [TAP5-672] - Translation for Vietnamese [TAP5-2013] - "Parameters" table often too wide in component javadocs [TAP5-2063] - Add support for multivalued parameters in Link [TAP5-2067] - Error loading classes with Tomcat 7 parallel deployment [TAP5-2097] - Use a _javascript_Stack to import the tapestry-beanvalidator.js file. [TAP5-2102] - Allow supplying EntityManager properties via TapestryPersistenceUnitInfo New Feature [TAP5-2055] - Polish translations Release Notes Change Notification Preferences View Online
[CONF] Apache Tapestry > Release Notes 5.4
Release Notes 5.4 Page edited by Bob Harner Comment: Added note about breaking change to MarkupWriterFactory interface. Changes (1) ... Tapestry's use of the [Javassist|http://www.csg.is.titech.ac.jp/~chiba/javassist/] bytecode library has been completely removed, along with many related services, such as [ClassFactory|http://tapestry.apache.org/5.3/apidocs/org/apache/tapestry5/ioc/services/ClassFactory.html], that were deprecated in 5.3. Use [PlasticProxyFactory|http://tapestry.apache.org/current/apidocs/org/apache/tapestry5/ioc/services/PlasticProxyFactory.html] instead. h3. MarkupWriterFactory API changed The [MarkupWriterFactory|http://tapestry.apache.org/current/apidocs/org/apache/tapestry5/services/MarkupWriterFactory.html] interface has a couple of new methods, added to support the HTML5 rules for element endings. If you have any classes that _implement_ MarkupWriterFactory (which is rare), they'll need to be modified to implement the new methods. h3. Injected Scripts at Bottom ... Full Content Release Notes 5.3.6 Release Notes This is the consolidated list of changes between Tapestry versions 5.3 and 5.4. To upgrade to 5.4, most users who are not using deprecated features will be able to just update the dependency version in their Maven POM file or Gradle build script (or download the new JAR files) and the new version will just work. However, please read carefully below before upgrading, and also review the How to Upgrade instructions. Incompatible APIs _javascript_Support Some existing methods of _javascript_Support were changed from returning void, to returning the _javascript_Support instance, to allow for chaining of calls. This interface is consumed by end-user code, but not generally implemented by end-user code. Breaking Features ClassFactory Removed Tapestry's use of the Javassist bytecode library has been completely removed, along with many related services, such as ClassFactory, that were deprecated in 5.3. Use PlasticProxyFactory instead. MarkupWriterFactory API changed The MarkupWriterFactory interface has a couple of new methods, added to support the HTML5 rules for element endings. If you have any classes that implement MarkupWriterFactory (which is rare), they'll need to be modified to implement the new methods. Injected Scripts at Bottom In prior versions of Tapestry, _javascript_ libraries injected into the page (via the @Import annotation, or via _javascript_Support), were injected into the element of the HTML page, either at the end of the element, or before any existing
[CONF] Apache Tapestry > Release Notes 5.3.5
Release Notes 5.3.5
Page edited by Bob Harner
Comment:
Renamed "Bug" section to "Fixed Bugs"
Changes (4)
...
For those developers not using Maven or Gradle, you'll be pleased that we now offer the option of a binary download containing Tapestry's modules and main dependencies. More details are on the [Download] page.
h2. Jira issues
{html}
Release Notes - Tapestry 5 - Version 5.3.5
Fixed Bugs
...
Tasks
...
Full Content
Release Notes 5.3.4 Release Notes Release Notes 5.3.6
This is the consolidated list of changes between Tapestry included in version 5.3.5. Tapestry 5.3.5 is a drop-in replacement for prior Tapestry 5.3 releases. To upgrade, just update the Maven dependency in you POM file (or download the new JAR file) and the new version will just work. However, please review the How to Upgrade instructions before upgrading.
This is a very modest bug fix release, including a number of minor performance improvements. Importantly, the bundled version of Prototype is now 1.7.1, which includes some significant improvements and bug fixes that target Internet Explorer. However, the prototype change may affect the functionality of the Tapestry DateField component under some versions of Internet Explorer (this issue was discovered late in the voting process).
For those developers not using Maven or Gradle, you'll be pleased that we now offer the option of a binary download containing Tapestry's modules and main dependencies. More details are on the Download page.
Fixed Bugs
[TAP5-1601] - Sometime a method that references a field with a conduit will not be instrumented, resulting in an NPE accessing the field itself
[TAP5-1859] - Clicking a submit or button in a non-Tapestry Form causes a client exception
[TAP5-1868] - SRSCachingInterceptor returns compressed version of asset for all clients once it was compressed for some client
[TAP5-1887] - Client-side _javascript_ error if console.info/debug/... is available but not a function
[TAP5-1907] - Client exception in IE9 when partial page render introduces stylesheets
[TAP5-1949] - Alerts component does not show alerts added from a component that occurs later in the template
[TAP5-1973] - :443 added to URLs when using the Link.toAbsoluteURI(true)
[TAP5-1976] - XML Parser adds attributes with default values and produces invalid HTML5 markup
[TAP5-1977] - Memory leak (perm gen) in component reloading
[TAP5-1979] - Changing the implementation of a method after adding method advice does not work; the original implementation remains
[TAP5-1983] - PerThreadManager does not cleanup on shutdown, can lead to memory leaks when application redeployed
[TAP5-1991] - YUICompressor should be less verbose about common warnings
[TAP5-1992] - Switch YUICompressor dependency back to com.yahoo version 2.4.7
Tasks
[TAP5-1989] - Upgrade bundled Prototype to version 1.7.1
Release Notes 5.3.4 Release Notes Release Notes 5.3.6
Change Notification Preferences
View Online
|
View Changes
[CONF] Apache Tapestry > Release Notes 5.3.6
Release Notes 5.3.6 Page edited by Bob Harner Comment: Renamed "Bug" section to "Fixed Bugs" Changes (2) ... Release Notes - Tapestry 5 - Version 5.3.6 Fixed Bugs ... Improvements ... Full Content Release Notes 5.3.5 Release Notes Release Notes 5.4 This is the consolidated list of changes between Tapestry versions 5.3.5 and 5.3.6. Tapestry 5.3.6 is a drop-in replacement for prior Tapestry 5.3 releases. To upgrade, just update the Maven dependency in your POM file (or download the new JAR file) and the new version will just work. However, please review the How to Upgrade instructions before upgrading. This is a very modest bug fix release. Importantly, the bundled version of Prototype has been downgraded back to version 1.7, as the new version was causing a number of issues, especially under Internet Explorer. The main improvement is security related; Tapestry will now integrate a hash-based message authentication code (HMAC) into serialized Java object data stored on the client (generally, this means the t:formdata hidden field used by the Form component). When you first run your application under 5.3.6, you will see an alert and a console error concerning the HMAC configuration. You should update your application's configuration to set a unique, private value for the tapestry.hmac-passphrase configuration symbol. And, as with any Tapestry upgrade, be sure to change your application's version number. Jira issues Release Notes - Tapestry 5 - Version 5.3.6 Fixed Bugs [TAP5-986] - A request can fail with an NPE in some cases, when a Tapestry page is acting as the servlet container error page [TAP5-1735] - Most packages lack package-level javadocs [TAP5-1903] - Client-side exception when a Zone containing a Form with an Upload component is re-rendered [TAP5-2008] - Serialized object data stored on the client should be HMAC signed and validated [TAP5-2009] - Downgrade bundled Prototype version back to 1.7 [TAP5-2010] - Broken links in Javadoc pages Improvements [TAP5-1996] - Add Severity.SUCCESS enum for alerts Release Notes 5.3.5 Release Notes Release Notes 5.4 Change Notification Preferences View Online | View Changes
[CONF] Apache Tapestry > Release Notes 5.3.6
Release Notes 5.3.6 Page edited by Howard M. Lewis Ship Comment: Reference the FAQ about upgrading Changes (1) ... When you first run your application under 5.3.6, you will see an alert and a console error concerning the HMAC configuration. You should update your application's configuration to set a unique, private value for the [tapestry.hmac-passphrase|Configuration] configuration symbol. And, as with any Tapestry upgrade, be sure to change your [application's version number|General Questions]. h2. Jira issues ... Full Content Release Notes 5.3.5 Release Notes Release Notes 5.4 This is the consolidated list of changes between Tapestry versions 5.3.5 and 5.3.6. Tapestry 5.3.6 is a drop-in replacement for prior Tapestry 5.3 releases. To upgrade, just update the Maven dependency in your POM file (or download the new JAR file) and the new version will just work. However, please review the How to Upgrade instructions before upgrading. This is a very modest bug fix release. Importantly, the bundled version of Prototype has been downgraded back to version 1.7, as the new version was causing a number of issues, especially under Internet Explorer. The main improvement is security related; Tapestry will now integrate a hash-based message authentication code (HMAC) into serialized Java object data stored on the client (generally, this means the t:formdata hidden field used by the Form component). When you first run your application under 5.3.6, you will see an alert and a console error concerning the HMAC configuration. You should update your application's configuration to set a unique, private value for the tapestry.hmac-passphrase configuration symbol. And, as with any Tapestry upgrade, be sure to change your application's version number. Jira issues Release Notes - Tapestry 5 - Version 5.3.6 Bug [TAP5-986] - A request can fail with an NPE in some cases, when a Tapestry page is acting as the servlet container error page [TAP5-1735] - Most packages lack package-level javadocs [TAP5-1903] - Client-side exception when a Zone containing a Form with an Upload component is re-rendered [TAP5-2008] - Serialized object data stored on the client should be HMAC signed and validated [TAP5-2009] - Downgrade bundled Prototype version back to 1.7 [TAP5-2010] - Broken links in Javadoc pages Improvement [TAP5-1996] - Add Severity.SUCCESS enum for alerts Release Notes 5.3.5 Release Notes Release Notes 5.4 Change Notification Preferences View Online | View Changes
[CONF] Apache Tapestry > Release Notes 5.3.6
Release Notes 5.3.6
Page edited by Bob Harner
Comment:
Mentioned HMAC needing to be private
Changes (1)
...
The main improvement is security related; Tapestry will now integrate a [hash-based message authentication code|http://en.wikipedia.org/wiki/HMAC] (HMAC) into serialized Java object data stored on the client (generally, this means the {{t:formdata}} hidden field used by the Form component).
When you first run your application under 5.3.6, you will see an alert and a console error concerning the HMAC configuration. You should update your application's configuration to set a unique, private value for the [tapestry.hmac-passphrase|Configuration] configuration symbol.
h2. Jira issues
...
Full Content
Release Notes 5.3.5 Release Notes Release Notes 5.4
This is the consolidated list of changes between Tapestry versions 5.3.5 and 5.3.6. Tapestry 5.3.6 is a drop-in replacement for prior Tapestry 5.3 releases. To upgrade, just update the Maven dependency in your POM file (or download the new JAR file) and the new version will just work. However, please review the How to Upgrade instructions before upgrading.
This is a very modest bug fix release. Importantly, the bundled version of Prototype has been downgraded back to version 1.7, as the new version was causing a number of issues, especially under Internet Explorer.
The main improvement is security related; Tapestry will now integrate a hash-based message authentication code (HMAC) into serialized Java object data stored on the client (generally, this means the t:formdata hidden field used by the Form component).
When you first run your application under 5.3.6, you will see an alert and a console error concerning the HMAC configuration. You should update your application's configuration to set a unique, private value for the tapestry.hmac-passphrase configuration symbol.
Jira issues
Release Notes - Tapestry 5 - Version 5.3.6
Bug
[TAP5-986] - A request can fail with an NPE in some cases, when a Tapestry page is acting as the servlet container error page
[TAP5-1735] - Most packages lack package-level javadocs
[TAP5-1903] - Client-side exception when a Zone containing a Form with an Upload component is re-rendered
[TAP5-2008] - Serialized object data stored on the client should be HMAC signed and validated
[TAP5-2009] - Downgrade bundled Prototype version back to 1.7
[TAP5-2010] - Broken links in Javadoc pages
Improvement
[TAP5-1996] - Add Severity.SUCCESS enum for alerts
Release Notes 5.3.5 Release Notes Release Notes 5.4
Change Notification Preferences
View Online
|
View Changes
[CONF] Apache Tapestry > Release Notes
Release Notes Page edited by Howard M. Lewis Ship Changes (2) ... ||Release || Release Notes || Status || Released | | Tapestry 5.4 | [Release Notes for 5.4|Release Notes 5.4] | *Under Development* | | | Tapestry 5.3.6 | [Release Notes for 5.3.6|Release Notes 5.3.6] | *Current Stable Release* | 12 Oct 2012 | | Tapestry 5.3.5 | [Release Notes for 5.3.5|Release Notes 5.3.5] | *Current Stable Release* | 29 Aug 2012 | | Tapestry 5.3.4 | [Release Notes for 5.3.4|Release Notes 5.3.4] | | 16 Jul 2012 | | Tapestry 5.3.3 | [Release Notes for 5.3.3|Release Notes 5.3.3] | | 24 Apr 2012 | ... Full Content These release notes provide the details of the changes in each Tapestry version. Be sure to read How to Upgrade too. Release Release Notes Status Released Tapestry 5.4 Release Notes for 5.4 Under Development Tapestry 5.3.6 Release Notes for 5.3.6 Current Stable Release 12 Oct 2012 Tapestry 5.3.5 Release Notes for 5.3.5 29 Aug 2012 Tapestry 5.3.4 Release Notes for 5.3.4 16 Jul 2012 Tapestry 5.3.3 Release Notes for 5.3.3 24 Apr 2012 Tapestry 5.3.2 Release Notes for 5.3.2 07 Feb 2012 Tapestry 5.3.1 Release Notes for 5.3.1 21 Dec 2011 Tapestry 5.3 Release Notes for 5.3 21 Nov 2011 Tapestry 5.2.6 Release Notes for 5.2.6 22 Jun 2011 Tapestry 5.1 Release Notes for 5.1.0.5 12 Apr 2009 Tapestry 5.0 Release Notes for 5.0.19 Dec 2008 Change Notification Preferences View Online | View Changes
[CONF] Apache Tapestry > Release Notes 5.3.6
Release Notes 5.3.6
Page edited by Howard M. Lewis Ship
Changes (2)
...
This is a very modest bug fix release. Importantly, the bundled version of [Prototype|http://prototypejs.org/2012/8/8/prototype-1-7-1] has been downgraded back to version 1.7, as the new version was causing a number of issues, especially under Internet Explorer.
The main improvement is security related; Tapestry will now integrate a [hash-based message authentication code|http://en.wikipedia.org/wiki/HMAC] into an serialized Java object data stored on the client; generally, this means the {{t:formdata}} hidden field used by the Form component.
When you first run your application under 5.3.6, you will see an alert and a console error concerning the HMAC configuration. You should update your application's configuration to set a unique value for [configuration symbol tapestry.hmac-passphrase|Configuration].
For those developers not using Maven or Gradle, you'll be pleased that we now offer the option of a binary download containing Tapestry's modules and main dependencies. More details are on the [Download] page.
h2. Jira issues
...
Full Content
Release Notes 5.3.5 Release Notes Release Notes 5.4
This is the consolidated list of changes between Tapestry included in version 5.3.6. Tapestry 5.3.6 is a drop-in replacement for prior Tapestry 5.3 releases. To upgrade, just update the Maven dependency in you POM file (or download the new JAR file) and the new version will just work. However, please review the How to Upgrade instructions before upgrading.
This is a very modest bug fix release. Importantly, the bundled version of Prototype has been downgraded back to version 1.7, as the new version was causing a number of issues, especially under Internet Explorer.
The main improvement is security related; Tapestry will now integrate a hash-based message authentication code into an serialized Java object data stored on the client; generally, this means the t:formdata hidden field used by the Form component.
When you first run your application under 5.3.6, you will see an alert and a console error concerning the HMAC configuration. You should update your application's configuration to set a unique value for configuration symbol tapestry.hmac-passphrase.
Jira issues
Release Notes - Tapestry 5 - Version 5.3.6
Bug
[TAP5-986] - A request can fail with an NPE in some cases, when a Tapestry page is acting as the servlet container error page
[TAP5-1735] - Most packages lack package-level javadocs
[TAP5-1903] - Client-side exception when a Zone containing a Form with an Upload component is re-rendered
[TAP5-2008] - Serialized object data stored on the client should be HMAC signed and validated
[TAP5-2009] - Downgrade bundled Prototype version back to 1.7
[TAP5-2010] - Broken links in Javadoc pages
Improvement
[TAP5-1996] - Add Severity.SUCCESS enum for alerts
Release Notes 5.3.5 Release Notes Release Notes 5.4
Change Notification Preferences
View Online
|
View Changes
[CONF] Apache Tapestry > Release Notes 5.3.6
Release Notes 5.3.6
Page added by Howard M. Lewis Ship
Release Notes
This is the consolidated list of changes between Tapestry included in version 5.3.6. Tapestry 5.3.6 is a drop-in replacement for prior Tapestry 5.3 releases. To upgrade, just update the Maven dependency in you POM file (or download the new JAR file) and the new version will just work. However, please review the How to Upgrade instructions before upgrading.
This is a very modest bug fix release. Importantly, the bundled version of Prototype has been downgraded back to version 1.7, as the new version was causing a number of issues, especially under Internet Explorer.
The main improvement is security related; Tapestry will now integrate a hash-based message authentication code into an serialized Java object data stored on the client; generally, this means the
Unknown macro: {t}
hidden field used by the Form component.
When you first run your application under 5.3.6, you will see an alert and a console error concerning the HMAC configuration. You should update your application's configuration to set a unique value for configuration symbol tapestry.hmac-passphrase.
For those developers not using Maven or Gradle, you'll be pleased that we now offer the option of a binary download containing Tapestry's modules and main dependencies. More details are on the Download page.
Jira issues
Release Notes - Tapestry 5 - Version 5.3.6
Bug
[TAP5-986] - A request can fail with an NPE in some cases, when a Tapestry page is acting as the servlet container error page
[TAP5-1735] - Most packages lack package-level javadocs
[TAP5-1903] - Client-side exception when a Zone containing a Form with an Upload component is re-rendered
[TAP5-2008] - Serialized object data stored on the client should be HMAC signed and validated
[TAP5-2009] - Downgrade bundled Prototype version back to 1.7
[TAP5-2010] - Broken links in Javadoc pages
Improvement
[TAP5-1996] - Add Severity.SUCCESS enum for alerts
Release Notes
Change Notification Preferences
View Online
[CONF] Apache Tapestry > Release Notes 5.3.5
Release Notes 5.3.5 Page edited by Howard M. Lewis Ship Changes (1) ... This is the consolidated list of changes between Tapestry included in version 5.3.5. Tapestry 5.3.5 is a drop-in replacement for prior Tapestry 5.3 releases. To upgrade, just update the Maven dependency in you POM file (or [download|Download] the new JAR file) and the new version will just work. However, please review the [How to Upgrade] instructions before upgrading. This is a very modest bug fix release, including a number of minor performance improvements. Importantly, the bundled version of [Prototype|http://prototypejs.org/2012/8/8/prototype-1-7-1] is now 1.7.1, which includes some significant improvements and bug fixes that target Internet Explorer. However, the prototype change _may_ affect the functionality of the Tapestry DateField component under some versions of Internet Explorer (this issue was discovered late in the voting process). For those developers not using Maven or Gradle, you'll be pleased that we now offer the option of a binary download containing Tapestry's modules and main dependencies. More details are on the [Download] page. ... Full Content Release Notes 5.3.4 Release Notes Release Notes 5.4 This is the consolidated list of changes between Tapestry included in version 5.3.5. Tapestry 5.3.5 is a drop-in replacement for prior Tapestry 5.3 releases. To upgrade, just update the Maven dependency in you POM file (or download the new JAR file) and the new version will just work. However, please review the How to Upgrade instructions before upgrading. This is a very modest bug fix release, including a number of minor performance improvements. Importantly, the bundled version of Prototype is now 1.7.1, which includes some significant improvements and bug fixes that target Internet Explorer. However, the prototype change may affect the functionality of the Tapestry DateField component under some versions of Internet Explorer (this issue was discovered late in the voting process). For those developers not using Maven or Gradle, you'll be pleased that we now offer the option of a binary download containing Tapestry's modules and main dependencies. More details are on the Download page. Jira issues Release Notes - Tapestry 5 - Version 5.3.5 Bug [TAP5-1601] - Sometime a method that references a field with a conduit will not be instrumented, resulting in an NPE accessing the field itself [TAP5-1859] - Clicking a submit or button in a non-Tapestry Form causes a client exception [TAP5-1868] - SRSCachingInterceptor returns compressed version of asset for all clients once it was compressed for some client [TAP5-1887] - Client-side _javascript_ error if console.info/debug/... is available but not a function [TAP5-1907] - Client exception in IE9 when partial page render introduces stylesheets [TAP5-1949] - Alerts component does not show alerts added from a component that occurs later in the template [TAP5-1973] - :443 added to URLs when using the Link.toAbsoluteURI(true) [TAP5-1976] - XML Parser adds attributes with default values and produces invalid HTML5 markup [TAP5-1977] - Memory leak (perm gen) in component reloading [TAP5-1979] - Changing the implementation of a method after adding method advice does not work; the original implementation remains [TAP5-1983] - PerThreadManager does not cleanup on shutdown, can lead to memory leaks when application redeployed [TAP5-1991] - YUICompressor should be less verbose about common warnings [TAP5-1992] - Switch YUICompressor dependency back to com.yahoo version 2.4.7 Task [TAP5-1989] - Upgrade bundled Prototype to version 1.7.1 Release Notes 5.3.4 Release Notes Release Notes 5.4 Change Notification Preferences View Online | View Changes
[CONF] Apache Tapestry > Release Notes
Release Notes Page edited by Howard M. Lewis Ship Changes (2) ... ||Release || Release Notes || Status || Released | | Tapestry 5.4 | [Release Notes for 5.4|Release Notes 5.4] | *Under Development* | | | Tapestry 5.3.5 | [Release Notes for 5.3.5|Release Notes 5.3.5] | *Vote Underway* *Current Stable Release* | 209 Aug 2012 | | Tapestry 5.3.4 | [Release Notes for 5.3.4|Release Notes 5.3.4] | *Current Stable Release* | 16 Jul 2012 | | Tapestry 5.3.3 | [Release Notes for 5.3.3|Release Notes 5.3.3] | | 24 Apr 2012 | | Tapestry 5.3.2 | [Release Notes for 5.3.2|Release Notes 5.3.2] | | 07 Feb 2012 | ... Full Content These release notes provide the details of the changes in each Tapestry version. Be sure to read How to Upgrade too. Release Release Notes Status Released Tapestry 5.4 Release Notes for 5.4 Under Development Tapestry 5.3.5 Release Notes for 5.3.5 Current Stable Release 29 Aug 2012 Tapestry 5.3.4 Release Notes for 5.3.4 16 Jul 2012 Tapestry 5.3.3 Release Notes for 5.3.3 24 Apr 2012 Tapestry 5.3.2 Release Notes for 5.3.2 07 Feb 2012 Tapestry 5.3.1 Release Notes for 5.3.1 21 Dec 2011 Tapestry 5.3 Release Notes for 5.3 21 Nov 2011 Tapestry 5.2.6 Release Notes for 5.2.6 22 Jun 2011 Tapestry 5.1 Release Notes for 5.1.0.5 12 Apr 2009 Tapestry 5.0 Release Notes for 5.0.19 Dec 2008 Change Notification Preferences View Online | View Changes
[CONF] Apache Tapestry > Release Notes 5.3.5
Release Notes 5.3.5 Page edited by Howard M. Lewis Ship Changes (2) ... [Under as yet unknown circumstances, Sometime a method that references a field with a conduit will not be instrumented, resulting in an NPE accessing the field itself [ ... [ [ ... Full Content Release Notes 5.3.4 Release Notes Release Notes 5.4 This is the consolidated list of changes between Tapestry included in version 5.3.5. Tapestry 5.3.5 is a drop-in replacement for prior Tapestry 5.3 releases. To upgrade, just update the Maven dependency in you POM file (or download the new JAR file) and the new version will just work. However, please review the How to Upgrade instructions before upgrading. This is a very modest bug fix release, including a number of minor performance improvements. Importantly, the bundled version of Prototype is now 1.7.1, which includes some significant improvements and bug fixes that target Internet Explorer. For those developers not using Maven or Gradle, you'll be pleased that we now offer the option of a binary download containing Tapestry's modules and main dependencies. More details are on the Download page. Jira issues Release Notes - Tapestry 5 - Version 5.3.5 Bug [TAP5-1601] - Sometime a method that references a field with a conduit will not be instrumented, resulting in an NPE accessing the field itself [TAP5-1859] - Clicking a submit or button in a non-Tapestry Form causes a client exception [TAP5-1868] - SRSCachingInterceptor returns compressed version of asset for all clients once it was compressed for some client [TAP5-1887] - Client-side _javascript_ error if console.info/debug/... is available but not a function [TAP5-1907] - Client exception in IE9 when partial page render introduces stylesheets [TAP5-1949] - Alerts component does not show alerts added from a component that occurs later in the template [TAP5-1973] - :443 added to URLs when using the Link.toAbsoluteURI(true) [TAP5-1976] - XML Parser adds attributes with default values and produces invalid HTML5 markup [TAP5-1977] - Memory leak (perm gen) in component reloading [TAP5-1979] - Changing the implementation of a method after adding method advice does not work; the original implementation remains [TAP5-1983] - PerThreadManager does not cleanup on shutdown, can lead to memory leaks when application redeployed [TAP5-1991] - YUICompressor should be less verbose about common warnings [TAP5-1992] - Switch YUICompressor dependency back to com.yahoo version 2.4.7 Task [TAP5-1989] - Upgrade bundled Prototype to version 1.7.1 Release Notes 5.3.4 Release Notes Release Notes 5.4 Change Notification Preferences View Online | View Changes
[CONF] Apache Tapestry > Release Notes
Release Notes Page edited by Howard M. Lewis Ship Changes (1) ... ||Release || Release Notes || Status || Released | | Tapestry 5.4 | [Release Notes for 5.4|Release Notes 5.4] | *Under Development* | | | Tapestry 5.3.5 | [Release Notes for 5.3.5|Release Notes 5.3.5] | *Current Under Vote* *Vote Underway* | 20 Aug 2012 | | Tapestry 5.3.4 | [Release Notes for 5.3.4|Release Notes 5.3.4] | *Current Stable Release* | 16 Jul 2012 | | Tapestry 5.3.3 | [Release Notes for 5.3.3|Release Notes 5.3.3] | | 24 Apr 2012 | ... Full Content These release notes provide the details of the changes in each Tapestry version. Be sure to read How to Upgrade too. Release Release Notes Status Released Tapestry 5.4 Release Notes for 5.4 Under Development Tapestry 5.3.5 Release Notes for 5.3.5 Vote Underway 20 Aug 2012 Tapestry 5.3.4 Release Notes for 5.3.4 Current Stable Release 16 Jul 2012 Tapestry 5.3.3 Release Notes for 5.3.3 24 Apr 2012 Tapestry 5.3.2 Release Notes for 5.3.2 07 Feb 2012 Tapestry 5.3.1 Release Notes for 5.3.1 21 Dec 2011 Tapestry 5.3 Release Notes for 5.3 21 Nov 2011 Tapestry 5.2.6 Release Notes for 5.2.6 22 Jun 2011 Tapestry 5.1 Release Notes for 5.1.0.5 12 Apr 2009 Tapestry 5.0 Release Notes for 5.0.19 Dec 2008 Change Notification Preferences View Online | View Changes
[CONF] Apache Tapestry > Release Notes
Release Notes Page edited by Howard M. Lewis Ship Changes (1) ... ||Release || Release Notes || Status || Released | | Tapestry 5.4 | [Release Notes for 5.4|Release Notes 5.4] | *Under Development* | | | Tapestry 5.3.5 | [Release Notes for 5.3.5|Release Notes 5.3.5] | *Current Under Vote* | 20 Aug 2012 | | Tapestry 5.3.4 | [Release Notes for 5.3.4|Release Notes 5.3.4] | *Current Stable Release* | 16 Jul 2012 | | Tapestry 5.3.3 | [Release Notes for 5.3.3|Release Notes 5.3.3] | | 24 Apr 2012 | ... Full Content These release notes provide the details of the changes in each Tapestry version. Be sure to read How to Upgrade too. Release Release Notes Status Released Tapestry 5.4 Release Notes for 5.4 Under Development Tapestry 5.3.5 Release Notes for 5.3.5 Current Under Vote 20 Aug 2012 Tapestry 5.3.4 Release Notes for 5.3.4 Current Stable Release 16 Jul 2012 Tapestry 5.3.3 Release Notes for 5.3.3 24 Apr 2012 Tapestry 5.3.2 Release Notes for 5.3.2 07 Feb 2012 Tapestry 5.3.1 Release Notes for 5.3.1 21 Dec 2011 Tapestry 5.3 Release Notes for 5.3 21 Nov 2011 Tapestry 5.2.6 Release Notes for 5.2.6 22 Jun 2011 Tapestry 5.1 Release Notes for 5.1.0.5 12 Apr 2009 Tapestry 5.0 Release Notes for 5.0.19 Dec 2008 Change Notification Preferences View Online | View Changes
[CONF] Apache Tapestry > Release Notes 5.3.5
Release Notes 5.3.5
Page edited by Howard M. Lewis Ship
Changes (2)
{scrollbar}
This is the consolidated list of changes between Tapestry versions 5.3.3 and 5.3.4. included in version 5.3.5. Tapestry 5.3.45 is a drop-in replacement for prior Tapestry 5.3 releases. To upgrade, just update the Maven dependency in you POM file (or [download|Download] the new JAR file) and the new version will just work. However, please review the [How to Upgrade] instructions before upgrading.
This is a very modest bug fix release, including a number of minor performance improvements. Importantly, the bundled version of [Prototype|http://prototypejs.org/2012/8/8/prototype-1-7-1] is now 1.7.1, which includes some significant improvements and bug fixes that target Internet Explorer.
For those developers not using Maven or Gradle, you'll be pleased that we now offer the option of a binary download containing Tapestry's modules and main dependencies. More details are on the [Download] page.
...
Full Content
Release Notes 5.3.4 Release Notes Release Notes 5.4
This is the consolidated list of changes between Tapestry included in version 5.3.5. Tapestry 5.3.5 is a drop-in replacement for prior Tapestry 5.3 releases. To upgrade, just update the Maven dependency in you POM file (or download the new JAR file) and the new version will just work. However, please review the How to Upgrade instructions before upgrading.
This is a very modest bug fix release, including a number of minor performance improvements. Importantly, the bundled version of Prototype is now 1.7.1, which includes some significant improvements and bug fixes that target Internet Explorer.
For those developers not using Maven or Gradle, you'll be pleased that we now offer the option of a binary download containing Tapestry's modules and main dependencies. More details are on the Download page.
Jira issues
Release Notes - Tapestry 5 - Version 5.3.5
Bug
[TAP5-1601] - Under as yet unknown circumstances, a method that references a field with a conduit will not be instrumented, resulting in an NPE accessing the field itself
[TAP5-1859] - Clicking a submit or button in a non-Tapestry Form causes a client exception
[TAP5-1868] - SRSCachingInterceptor returns compressed version of asset for all clients once it was compressed for some client
[TAP5-1887] - Client-side _javascript_ error if console.info/debug/... is available but not a function
[TAP5-1907] - Client exception in IE9 when partial page render introduces stylesheets
[TAP5-1949] - Alerts component does not show alerts added from a component that occurs later in the template
[TAP5-1973] - :443 added to URLs when using the Link.toAbsoluteURI(true)
[TAP5-1976] - XML Parser adds attributes with default values and produces invalid HTML5 markup
[TAP5-1977] - Memory leak (perm gen) in component reloading
[TAP5-1979] - Changing the implementation of a method after adding method advice does not work; the original implementation remains
[TAP5-1983] - PerThreadManager does not cleanup on shutdown, can lead to memory leaks when application redeployed
[TAP5-1991] - YUICompressor should be less verbose about common warnings
Task
[TAP5-1989] - Upgrade bundled Prototype to version 1.7.1
Release Notes 5.3.4 Release Notes Release Notes 5.4
Change Notification Preferences
View Online
|
View Changes
[CONF] Apache Tapestry > Release Notes 5.3.5
Release Notes 5.3.5
Page edited by Howard M. Lewis Ship
Changes (2)
{scrollbar}
This is the consolidated list of changes between Tapestry versions 5.3.3 and 5.3.4. Tapestry 5.3.4 is a drop-in replacement for prior Tapestry 5.3 releases. To upgrade, just update the Maven dependency in you POM file (or [download|Download] the new JAR file) and the new version will just work. However, please review the [How to Upgrade] instructions before upgrading. This is a very modest bug fix release, including a number of minor performance improvements. For those developers not using Maven or Gradle, you'll be pleased that we now offer the option of a binary download containing Tapestry's modules and main dependencies. More details are on the [Download] page. h2. Jira issues {html} Release Notes - Tapestry 5 - Version 5.3.5 Bug [ [ [ [ [ [ [ [ [ [ [ [ Task [ {html} {scrollbar}
Full Content
Release Notes 5.3.4 Release Notes Release Notes 5.4
This is the consolidated list of changes between Tapestry versions 5.3.3 and 5.3.4. Tapestry 5.3.4 is a drop-in replacement for prior Tapestry 5.3 releases. To upgrade, just update the Maven dependency in you POM file (or download the new JAR file) and the new version will just work. However, please review the How to Upgrade instructions before upgrading.
This is a very modest bug fix release, including a number of minor performance improvements.
For those developers not using Maven or Gradle, you'll be pleased that we now offer the option of a binary download containing Tapestry's modules and main dependencies. More details are on the Download page.
Jira issues
Release Notes - Tapestry 5 - Version 5.3.5
Bug
[TAP5-1601] - Under as yet unknown circumstances, a method that references a field with a conduit will not be instrumented, resulting in an NPE accessing the field itself
[TAP5-1859] - Clicking a submit or button in a non-Tapestry Form causes a client exception
[TAP5-1868] - SRSCachingInterceptor returns compressed version of asset for all clients once it was compressed for some client
[TAP5-1887] - Client-side _javascript_ error if console.info/debug/... is available but not a function
[TAP5-1907] - Client exception in IE9 when partial page render introduces stylesheets
[TAP5-1949] - Alerts component does not show alerts added from a component that occurs later in the template
[TAP5-1973] - :443 added to URLs when using the Link.toAbsoluteURI(true)
[TAP5-1976] - XML Parser adds attributes with default values and produces invalid HTML5 markup
[TAP5-1977] - Memory leak (perm gen) in component reloading
[TAP5-1979] - Changing the implementation of a method after adding method advice does not work; the original implementation remains
[TAP5-1983] - PerThreadManager does not cleanup on shutdown, can lead to memory leaks when application redeployed
[TAP5-1991] - YUICompressor should be less verbose about common warnings
Task
[TAP5-1989] - Upgrade bundled Prototype to version 1.7.1
Release Notes 5.3.4 Release Notes Release Notes 5.4
Change Notification Preferences
View Online
|
View Changes
[CONF] Apache Tapestry > Release Notes 5.3.5
Release Notes 5.3.5 Page added by Howard M. Lewis Ship Change Notification Preferences View Online
[CONF] Apache Tapestry > Release Notes 5.4
Release Notes 5.4 Page edited by Howard M. Lewis Ship Changes (3) ... h3. Injected Scripts at Bottom In prior versions of Tapestry, _javascript_ libraries injected into the page (via the @[Import|http://tapestry.apache.org/current/apidocs/org/apache/tapestry5/annotations/Import.html] annotation, or via [_javascript_Support|http://tapestry.apache.org/current/apidocs/org/apache/tapestry5/services/_javascript_/_javascript_Support.html]), were injected into the element of the HTML page, either at the end of the element, or before any existing
[CONF] Apache Tapestry > Release Notes
Release Notes Page edited by Howard M. Lewis Ship Changes (2) ... ||Release || Release Notes || Status || Released | | Tapestry 5.4 | [Release Notes for 5.4|Release Notes 5.4] | *Under Development* | | | Tapestry 5.3.4 | [Release Notes for 5.3.4|Release Notes 5.3.4] | *Vote Underway* *Current Stable Release* | 07 16 Jul 2012 | | Tapestry 5.3.3 | [Release Notes for 5.3.3|Release Notes 5.3.3] | *Current stable release* | 24 Apr 2012 | | Tapestry 5.3.2 | [Release Notes for 5.3.2|Release Notes 5.3.2] | | 07 Feb 2012 | | Tapestry 5.3.1 | [Release Notes for 5.3.1|Release Notes 5.3.1] | | 21 Dec 2011 ... Full Content These release notes provide the details of the changes in each Tapestry version. Be sure to read How to Upgrade too. Release Release Notes Status Released Tapestry 5.4 Release Notes for 5.4 Under Development Tapestry 5.3.4 Release Notes for 5.3.4 Current Stable Release 16 Jul 2012 Tapestry 5.3.3 Release Notes for 5.3.3 24 Apr 2012 Tapestry 5.3.2 Release Notes for 5.3.2 07 Feb 2012 Tapestry 5.3.1 Release Notes for 5.3.1 21 Dec 2011 Tapestry 5.3 Release Notes for 5.3 21 Nov 2011 Tapestry 5.2.6 Release Notes for 5.2.6 22 Jun 2011 Tapestry 5.1 Release Notes for 5.1.0.5 12 Apr 2009 Tapestry 5.0 Release Notes for 5.0.19 Dec 2008 Change Notification Preferences View Online | View Changes
[CONF] Apache Tapestry > Release Notes 5.3.4
Release Notes 5.3.4
Page edited by Howard M. Lewis Ship
Changes (1)
...
{html}
Bug
...
[
[
[
...
{html}
...
Full Content
Release Notes 5.3.3 Release Notes Release Notes 5.4
This is the consolidated list of changes between Tapestry versions 5.3.3 and 5.3.4. Tapestry 5.3.4 is a drop-in replacement for prior Tapestry 5.3 releases. To upgrade, just update the Maven dependency in you POM file (or download the new JAR file) and the new version will just work. However, please review the How to Upgrade instructions before upgrading.
This is a very modest bug fix release, including a number of minor performance improvements.
For those developers not using Maven or Gradle, you'll be pleased that we now offer the option of a binary download containing Tapestry's modules and main dependencies. More details are on the Download page.
Jira issues
Bug
[TAP5-1729] - Sometimes YUICompressor can fail with java.util.EmptyStackException
[TAP5-1848] - tapestry-jpa ignores persistence provider from persistence.xml
[TAP5-1873] - _javascript_ execution exception is not logged
[TAP5-1880] - GZip compression should be disabled if the request is over http 1.0
[TAP5-1929] - High contention in method InternalComponentResourcesImpl.postRenderCleanup() and NamedSet.getValues()
[TAP5-1935] - ContextResource uses a deprecated File.toURL
[TAP5-1950] - ResourceStreamer sends SC_NOT_MODIFIED as an error, but it should be just status
[TAP5-1952] - _javascript_ Compressor should log warnings as well as errors, and identify the input clearly
[TAP5-1963] - Original exception lost in CommitAfterWorker upon abort
[TAP5-1964] - In production mode, placeholder timestamp needs to be limited to one-second accuracy
Task
[TAP5-1852] - Upgrade Plastic to use ASM 4.0
[TAP5-1972] - Missing LICENSE and NOTICE files
Release Notes 5.3.3 Release Notes Release Notes 5.4
Change Notification Preferences
View Online
|
View Changes
[CONF] Apache Tapestry > Release Notes 5.3.4
Release Notes 5.3.4 Page edited by Howard M. Lewis Ship Changes (1) ... [ [ ... Full Content Release Notes 5.3.3 Release Notes Release Notes 5.4 This is the consolidated list of changes between Tapestry versions 5.3.3 and 5.3.4. Tapestry 5.3.4 is a drop-in replacement for prior Tapestry 5.3 releases. To upgrade, just update the Maven dependency in you POM file (or download the new JAR file) and the new version will just work. However, please review the How to Upgrade instructions before upgrading. This is a very modest bug fix release, including a number of minor performance improvements. For those developers not using Maven or Gradle, you'll be pleased that we now offer the option of a binary download containing Tapestry's modules and main dependencies. More details are on the Download page. Jira issues Bug [TAP5-1729] - Sometimes YUICompressor can fail with java.util.EmptyStackException [TAP5-1848] - tapestry-jpa ignores persistence provider from persistence.xml [TAP5-1873] - _javascript_ execution exception is not logged [TAP5-1880] - GZip compression should be disabled if the request is over http 1.0 [TAP5-1935] - ContextResource uses a deprecated File.toURL [TAP5-1950] - ResourceStreamer sends SC_NOT_MODIFIED as an error, but it should be just status [TAP5-1952] - _javascript_ Compressor should log warnings as well as errors, and identify the input clearly [TAP5-1963] - Original exception lost in CommitAfterWorker upon abort [TAP5-1964] - In production mode, placeholder timestamp needs to be limited to one-second accuracy Task [TAP5-1852] - Upgrade Plastic to use ASM 4.0 [TAP5-1972] - Missing LICENSE and NOTICE files Release Notes 5.3.3 Release Notes Release Notes 5.4 Change Notification Preferences View Online | View Changes
[CONF] Apache Tapestry > Release Notes 5.3.3
Release Notes 5.3.3
Page edited by Howard M. Lewis Ship
Changes (1)
...
h2. Jira issues
{html}
Release Notes - Tapestry 5 - Version 5.3.3
Bug
...
Full Content
Release Notes 5.3.2 Release Notes Release Notes 5.3.4
This is the consolidated list of changes between Tapestry versions 5.3.2 and 5.3.3. Tapestry 5.3.3 is a drop-in replacement for prior Tapestry 5.3 releases. To upgrade, just update the Maven dependency in you POM file (or download the new JAR file) and the new version will just work. However, please review the How to Upgrade instructions before upgrading.
This is a very modest bug fix release, but it does straighten out a significant problem with Java component classes containing non-private fields.
For those developers not using Maven or Gradle, you'll be pleased to know that this release now includes the option of a binary download containing Tapestry's modules and main dependencies. More details are on the Download page.
Jira issues
Bug
[TAP5-1791] - On some JDKs, the complex regular _expression_ used by ComponentEventLinkEncoderImpl will cause a stack overflow
[TAP5-1836] - "LocalhostOnly" WhitelistAnalyzer check "0:0:0:0:0:0:0:1%0" ip address instead "0:0:0:0:0:0:0:1"
[TAP5-1844] - Datefield not fires onchange event on changes
[TAP5-1854] - AjaxComponentEventRequestHandler doesn't handle the case where a response has already be returned, and may append an empty JSON Object to the response
[TAP5-1860] - Access to protected component fields does not always reflect in subclasses
[TAP5-1881] - TypeCoercion from Number to Boolean returns false for any number that is an even multiple of 256
[TAP5-1895] - ValidationDecorator.insideLabel(...) is called after the removal of PropertyContext in PropertyEditor
[TAP5-1906] - Interaction between client-side validation and submit buttons can result in a server-side error parsing JSON array
Improvement
[TAP5-1827] - KaptchaField should have a parameter to allow it to operate as a visible text field rather than a password field
New Feature
[TAP5-1857] - Add a SubmitMode (for Submit and LinkSubmit components) for unconditionally submitting the form
Task
[TAP5-1790] - Update Tapestry build to create a binary release archive (in addition to a source and javadoc archive)
[TAP5-1909] - Update Underscore _javascript_ library to latest version 1.3.3
Release Notes 5.3.2 Release Notes Release Notes 5.3.4
Change Notification Preferences
View Online
|
View Changes
[CONF] Apache Tapestry > Release Notes
Release Notes Page edited by Howard M. Lewis Ship Changes (6) These release notes provide the details of the changes in each Tapestry version. Be sure to read [How to Upgrade] too. ||Release || Release Notes || Status || Released | | Tapestry 5.4 | [Release Notes for 5.4|Release Notes 5.4] | *Under Development* | | || | Tapestry 5.3.4 | [Release Notes for 5.3.3|Release Notes 5.3.4] | *Vote Underway* | 7 07 Jul 2012 | | Tapestry 5.3.3 | [Release Notes for 5.3.3|Release Notes 5.3.3] | *Current stable release* | 24 Apr 2012 | | Tapestry 5.3.2 | [Release Notes for 5.3.2|Release Notes 5.3.2] | | 07 Feb 2012 | | Tapestry 5.3.1 | [Release Notes for 5.3.1|Release Notes 5.3.1] | | 21 Dec 2011 | Tapestry 5.3 | [Release Notes for 5.3|Release Notes 5.3] | | 21 Nov 2011 || | Tapestry 5.2.6 | [Release Notes for 5.2.6|Release Notes 5.2] | | Released 22 Jun 2011 | || | Tapestry 5.1| [Release Notes for 5.1.0.5|Release Notes 5.1] | | Released 12 Apr 2009 | || | Tapestry 5.0| [Release Notes for 5.0.19|Release Notes 5.0] | | Released Dec 2008 | Full Content These release notes provide the details of the changes in each Tapestry version. Be sure to read How to Upgrade too. Release Release Notes Status Released Tapestry 5.4 Release Notes for 5.4 Under Development Tapestry 5.3.4 Release Notes for 5.3.3 Vote Underway 07 Jul 2012 Tapestry 5.3.3 Release Notes for 5.3.3 Current stable release 24 Apr 2012 Tapestry 5.3.2 Release Notes for 5.3.2 07 Feb 2012 Tapestry 5.3.1 Release Notes for 5.3.1 21 Dec 2011 Tapestry 5.3 Release Notes for 5.3 21 Nov 2011 Tapestry 5.2.6 Release Notes for 5.2.6 22 Jun 2011 Tapestry 5.1 Release Notes for 5.1.0.5 12 Apr 2009 Tapestry 5.0 Release Notes for 5.0.19 Dec 2008 Change Notification Preferences View Online | View Changes
[CONF] Apache Tapestry > Release Notes
Release Notes Page edited by Howard M. Lewis Ship Changes (1) ... || Tapestry 5.4 | [Release Notes for 5.4|Release Notes 5.4] | *Under Development* | | || Tapestry 5.3.4 | [Release Notes for 5.3.3|Release Notes 5.3.34] | *Vote Underway* | 7 Jul 2012 | || Tapestry 5.3.3 | [Release Notes for 5.3.3|Release Notes 5.3.3] | *Current stable release* | 24 Apr 2012 | || Tapestry 5.3.2 | [Release Notes for 5.3.2|Release Notes 5.3.2] | | 07 Feb 2012 | ... Full Content These release notes provide the details of the changes in each Tapestry version. Be sure to read How to Upgrade too. Tapestry 5.4 Release Notes for 5.4 Under Development Tapestry 5.3.4 Release Notes for 5.3.3 Vote Underway 7 Jul 2012 Tapestry 5.3.3 Release Notes for 5.3.3 Current stable release 24 Apr 2012 Tapestry 5.3.2 Release Notes for 5.3.2 07 Feb 2012 Tapestry 5.3.1 Release Notes for 5.3.1 21 Dec 2011 Tapestry 5.3 Release Notes for 5.3 21 Nov 2011 Tapestry 5.2.6 Release Notes for 5.2.6 Released 22 Jun 2011 Tapestry 5.1 Release Notes for 5.1.0.5 Released 12 Apr 2009 Tapestry 5.0 Release Notes for 5.0.19 Released Dec 2008 Change Notification Preferences View Online | View Changes
[CONF] Apache Tapestry > Release Notes 5.3.4
Release Notes 5.3.4
Page edited by Howard M. Lewis Ship
Changes (4)
{scrollbar}
This is the consolidated list of changes between Tapestry versions 5.3.3 and 5.3.4. Tapestry 5.3.4 is a drop-in replacement for prior Tapestry 5.3 releases. To upgrade, just update the Maven dependency in you POM file (or [download|Download] the new JAR file) and the new version will just work. However, please review the [How to Upgrade] instructions before upgrading.
This is a very modest bug fix release, including a number of minor performance improvements. For those developers not using Maven or Gradle, you'll be pleased to we now offer the option of a binary download containing Tapestry's modules and main dependencies. More details are on the [Download] page. h2. Jira issues
{html}
...
{html}
{scrollbar}
Full Content
Release Notes 5.3.3 Release Notes Release Notes 5.4
This is the consolidated list of changes between Tapestry versions 5.3.3 and 5.3.4. Tapestry 5.3.4 is a drop-in replacement for prior Tapestry 5.3 releases. To upgrade, just update the Maven dependency in you POM file (or download the new JAR file) and the new version will just work. However, please review the How to Upgrade instructions before upgrading.
This is a very modest bug fix release, including a number of minor performance improvements.
For those developers not using Maven or Gradle, you'll be pleased to we now offer the option of a binary download containing Tapestry's modules and main dependencies. More details are on the Download page.
Jira issues
Bug
[TAP5-1729] - Sometimes YUICompressor can fail with java.util.EmptyStackException
[TAP5-1848] - tapestry-jpa ignores persistence provider from persistence.xml
[TAP5-1873] - _javascript_ execution exception is not logged
[TAP5-1880] - GZip compression should be disabled if the request is over http 1.0
[TAP5-1935] - ContextResource uses a deprecated File.toURL
[TAP5-1950] - ResourceStreamer sends SC_NOT_MODIFIED as an error, but it should be just status
[TAP5-1952] - _javascript_ Compressor should log warnings as well as errors, and identify the input clearly
[TAP5-1963] - Original exception lost in CommitAfterWorker upon abort
[TAP5-1964] - In production mode, placeholder timestamp needs to be limited to one-second accuracy
Task
[TAP5-1852] - Upgrade Plastic to use ASM 4.0
Release Notes 5.3.3 Release Notes Release Notes 5.4
Change Notification Preferences
View Online
|
View Changes
[CONF] Apache Tapestry > Release Notes
Release Notes Page edited by Howard M. Lewis Ship Changes (1) ... || Tapestry 5.4 | [Release Notes for 5.4|Release Notes 5.4] | *Under Development* | | || Tapestry 5.3.4 | [Release Notes for 5.3.3|Release Notes 5.3.3] | *Vote Underway* | 7 Jul 2012 | || Tapestry 5.3.3 | [Release Notes for 5.3.3|Release Notes 5.3.3] | *Current stable release* | 24 Apr 2012 | || Tapestry 5.3.2 | [Release Notes for 5.3.2|Release Notes 5.3.2] | | 07 Feb 2012 | ... Full Content These release notes provide the details of the changes in each Tapestry version. Be sure to read How to Upgrade too. Tapestry 5.4 Release Notes for 5.4 Under Development Tapestry 5.3.4 Release Notes for 5.3.3 Vote Underway 7 Jul 2012 Tapestry 5.3.3 Release Notes for 5.3.3 Current stable release 24 Apr 2012 Tapestry 5.3.2 Release Notes for 5.3.2 07 Feb 2012 Tapestry 5.3.1 Release Notes for 5.3.1 21 Dec 2011 Tapestry 5.3 Release Notes for 5.3 21 Nov 2011 Tapestry 5.2.6 Release Notes for 5.2.6 Released 22 Jun 2011 Tapestry 5.1 Release Notes for 5.1.0.5 Released 12 Apr 2009 Tapestry 5.0 Release Notes for 5.0.19 Released Dec 2008 Change Notification Preferences View Online | View Changes
[CONF] Apache Tapestry > Release Notes 5.3.4
Release Notes 5.3.4 Page added by Howard M. Lewis Ship Bug [TAP5-1729] - Sometimes YUICompressor can fail with java.util.EmptyStackException [TAP5-1848] - tapestry-jpa ignores persistence provider from persistence.xml [TAP5-1873] - _javascript_ execution exception is not logged [TAP5-1880] - GZip compression should be disabled if the request is over http 1.0 [TAP5-1935] - ContextResource uses a deprecated File.toURL [TAP5-1950] - ResourceStreamer sends SC_NOT_MODIFIED as an error, but it should be just status [TAP5-1952] - _javascript_ Compressor should log warnings as well as errors, and identify the input clearly [TAP5-1963] - Original exception lost in CommitAfterWorker upon abort [TAP5-1964] - In production mode, placeholder timestamp needs to be limited to one-second accuracy Task [TAP5-1852] - Upgrade Plastic to use ASM 4.0 Change Notification Preferences View Online
[CONF] Apache Tapestry > Release Notes 5.4
Release Notes 5.4
Page edited by Howard M. Lewis Ship
Comment:
fix broken markup for some links
Changes (3)
{scrollbar}
This is the consolidated list of changes between Tapestry versions 5.3 and 5.4. To upgrade to 5.4, most users who are not using deprecated features will be able to just update the Maven dependency version in their Maven POM file or Gradle build script (or [download|Download] the new JAR files) and the new version will just work. However, please read carefully below before upgrading, and also review the [How to Upgrade] instructions.
h2. Incompatible APIs
...
h3. Injected Scripts at Bottom
In prior versions of Tapestry, _javascript_ libraries injected into the page (via the @[Import|http://tapestry.apache.org/current/apidocs/org/apache/tapestry5/annotations/Import.html] annotation, or via [_javascript_Support|http://tapestry.apache.org/current/apidocs/org/apache/tapestry5/services/_javascript_/_javascript_Support.html], were injected into the element of the HTML page, either at the end of the element, or before any existing
[CONF] Apache Tapestry > Release Notes 5.4
Release Notes 5.4 Page edited by Howard M. Lewis Ship Changes (3) ... h2. Breaking Features h3. ClassFactory Removed Tapestry's use of the [Javassist|http://www.csg.is.titech.ac.jp/~chiba/javassist/] bytecode library has been completely removed, along with many related services, such as [ClassFactory|http://tapestry.apache.org/5.3/apidocs/org/apache/tapestry5/ioc/services/ClassFactory.html], that were deprecated in 5.3. Use [PlasticProxyFactory|http://tapestry.apache.org/current/apidocs/org/apache/tapestry5/ioc/services/PlasticProxyFactory.html] instead. h3. Injected Scripts at Bottom In prior versions of Tapestry, _javascript_ libraries injected into the page (via the element of the HTML page, either at the end of the element, or before any existing
[CONF] Apache Tapestry > Release Notes 5.4
Release Notes 5.4 Page edited by Howard M. Lewis Ship Changes (1) ... This is the consolidated list of changes between Tapestry versions 5.3 and 5.4. To upgrade to 5.4, most users who are not using deprecated features will be able to just update the Maven dependency in their POM file (or [download|Download] the new JAR file) and the new version will just work. However, please read carefully below before upgrading, and also review the [How to Upgrade] instructions. h2. Incompatible APIs h3. _javascript_Support Some existing methods of _javascript_Support were changed from returning void, to returning the _javascript_Support instance, to allow for chaining of calls. This interface is consumed by end-user code, but not generally implemented by end-user code. h2. Breaking Features ... Full Content Release Notes 5.3.3 Release Notes This is the consolidated list of changes between Tapestry versions 5.3 and 5.4. To upgrade to 5.4, most users who are not using deprecated features will be able to just update the Maven dependency in their POM file (or download the new JAR file) and the new version will just work. However, please read carefully below before upgrading, and also review the How to Upgrade instructions. Incompatible APIs _javascript_Support Some existing methods of _javascript_Support were changed from returning void, to returning the _javascript_Support instance, to allow for chaining of calls. This interface is consumed by end-user code, but not generally implemented by end-user code. Breaking Features Tapestry's use of the Javassist bytecode library has been completely removed, along with many related services, such as ClassFactory, that were deprecated in 5.3. Use PlasticProxyFactory instead. No Redirect On Form Validation Errors In prior releases of Tapestry, when a client-side form was submitted and there were server-side validation errors, Tapestry would perform a redirect-after-post to re-render the page; this meant that the ValidationTracker object that stores validation errors would, itself, need to persist to the new render request, causing a server-side session to be created. Starting in 5.4, the default behavior for server-side validation exceptions is to re-render the page within the same request; this obviates the need to use a persistent field to store the tracker. New Features Component field visibility In prior versions of Tapestry, all instance fields of components had to be visibility private; starting with versions 5.3.2 and 5.4, this has been relaxed. Component fields may be protected, or package private (that is, no visibility modifier). Fields that are final, or annotated with @Retain may even be public. In any case, this makes it easier for pages to work with other pages in the same package, and for subclasses to more easily access the fields (including parameter fields, or injections) provided by base classes. This feature should be used with care, as it can lead to designs that are more difficult to maintain. Release Notes 5.3.3 Release Notes Change Notification Preferences View Online | View Changes
[CONF] Apache Tapestry > Release Notes 5.3.3
Release Notes 5.3.3
Page edited by Howard M. Lewis Ship
Changes (2)
{scrollbar}
This is the consolidated list of changes between Tapestry versions 5.3.2 and 5.3.3. Tapestry 5.3.2 is a drop-in replacement for Tapestry 5.3.2. To upgrade, just update the Maven dependency in you POM file (or [download|Download] the new JAR file) and the new version will just work. However, please review the [How to Upgrade] instructions before upgrading. And be sure to check the [Release Notes for 5.3|Release Notes 5.3] too.
This is the consolidated list of changes between Tapestry versions 5.3.2 and 5.3.3. Tapestry 5.3.3 is a drop-in replacement for prior Tapestry 5.3 releases. To upgrade, just update the Maven dependency in you POM file (or [download|Download] the new JAR file) and the new version will just work. However, please review the [How to Upgrade] instructions before upgrading.
This is a very modest bug fix release, but it does straighten out a significant problem with Java component classes containing non-private fields.
...
Full Content
Release Notes 5.3.2 Release Notes Release Notes 5.4
This is the consolidated list of changes between Tapestry versions 5.3.2 and 5.3.3. Tapestry 5.3.3 is a drop-in replacement for prior Tapestry 5.3 releases. To upgrade, just update the Maven dependency in you POM file (or download the new JAR file) and the new version will just work. However, please review the How to Upgrade instructions before upgrading.
This is a very modest bug fix release, but it does straighten out a significant problem with Java component classes containing non-private fields.
For those developers not using Maven or Gradle, you'll be pleased to know that this release now includes the option of a binary download containing Tapestry's modules and main dependencies. More details are on the Download page.
Jira issues
Release Notes - Tapestry 5 - Version 5.3.3
Bug
[TAP5-1791] - On some JDKs, the complex regular _expression_ used by ComponentEventLinkEncoderImpl will cause a stack overflow
[TAP5-1836] - "LocalhostOnly" WhitelistAnalyzer check "0:0:0:0:0:0:0:1%0" ip address instead "0:0:0:0:0:0:0:1"
[TAP5-1844] - Datefield not fires onchange event on changes
[TAP5-1854] - AjaxComponentEventRequestHandler doesn't handle the case where a response has already be returned, and may append an empty JSON Object to the response
[TAP5-1860] - Access to protected component fields does not always reflect in subclasses
[TAP5-1881] - TypeCoercion from Number to Boolean returns false for any number that is an even multiple of 256
[TAP5-1895] - ValidationDecorator.insideLabel(...) is called after the removal of PropertyContext in PropertyEditor
[TAP5-1906] - Interaction between client-side validation and submit buttons can result in a server-side error parsing JSON array
Improvement
[TAP5-1827] - KaptchaField should have a parameter to allow it to operate as a visible text field rather than a password field
New Feature
[TAP5-1857] - Add a SubmitMode (for Submit and LinkSubmit components) for unconditionally submitting the form
Task
[TAP5-1790] - Update Tapestry build to create a binary release archive (in addition to a source and javadoc archive)
[TAP5-1909] - Update Underscore _javascript_ library to latest version 1.3.3
Release Notes 5.3.2 Release Notes Release Notes 5.4
Change Notification Preferences
View Online
|
View Changes
[CONF] Apache Tapestry > Release Notes
Release Notes Page edited by Bob Harner Comment: Updated status on 5.3.3 Changes (3) These release notes provide the details of the changes in each Tapestry version. Be sure to read [How to Upgrade] too. || Tapestry 5.4 | [Release Notes for 5.4|Release Notes 5.4] | *Unreleased* *Under Development* | | || Tapestry 5.3.3 | [Release Notes for 5.3.3|Release Notes 5.3.3] | *Vote Underway* *Current stable release* | 17 24 Apr 2012 | || Tapestry 5.3.2 | [Release Notes for 5.3.2|Release Notes 5.3.2] | *Current stable release* | 07 Feb 2012 | || Tapestry 5.3.1 | [Release Notes for 5.3.1|Release Notes 5.3.1] | | 21 Dec 2011 || Tapestry 5.3 | [Release Notes for 5.3|Release Notes 5.3] | | 21 Nov 2011 ... Full Content These release notes provide the details of the changes in each Tapestry version. Be sure to read How to Upgrade too. Tapestry 5.4 Release Notes for 5.4 Under Development Tapestry 5.3.3 Release Notes for 5.3.3 Current stable release 24 Apr 2012 Tapestry 5.3.2 Release Notes for 5.3.2 07 Feb 2012 Tapestry 5.3.1 Release Notes for 5.3.1 21 Dec 2011 Tapestry 5.3 Release Notes for 5.3 21 Nov 2011 Tapestry 5.2.6 Release Notes for 5.2.6 Released 22 Jun 2011 Tapestry 5.1 Release Notes for 5.1.0.5 Released 12 Apr 2009 Tapestry 5.0 Release Notes for 5.0.19 Released Dec 2008 Change Notification Preferences View Online | View Changes
[CONF] Apache Tapestry > Release Notes
Release Notes Page edited by Howard M. Lewis Ship Changes (1) ... || Tapestry 5.4 | [Release Notes for 5.4|Release Notes 5.4] | *Unreleased* | | || Tapestry 5.3.3 | [Release Notes for 5.3.23|Release Notes 5.3.23] | *Vote Underway* | 17 Apr 2012 | || Tapestry 5.3.2 | [Release Notes for 5.3.2|Release Notes 5.3.2] | *Current stable release* | 07 Feb 2012 | || Tapestry 5.3.1 | [Release Notes for 5.3.1|Release Notes 5.3.1] | | 21 Dec 2011 ... Full Content These release notes provide the details of the changes in each Tapestry version. Be sure to read How to Upgrade too. Tapestry 5.4 Release Notes for 5.4 Unreleased Tapestry 5.3.3 Release Notes for 5.3.3 Vote Underway 17 Apr 2012 Tapestry 5.3.2 Release Notes for 5.3.2 Current stable release 07 Feb 2012 Tapestry 5.3.1 Release Notes for 5.3.1 21 Dec 2011 Tapestry 5.3 Release Notes for 5.3 21 Nov 2011 Tapestry 5.2.6 Release Notes for 5.2.6 Released 22 Jun 2011 Tapestry 5.1 Release Notes for 5.1.0.5 Released 12 Apr 2009 Tapestry 5.0 Release Notes for 5.0.19 Released Dec 2008 Change Notification Preferences View Online | View Changes
[CONF] Apache Tapestry > Release Notes
Release Notes Page edited by Howard M. Lewis Ship Changes (1) ... || Tapestry 5.4 | [Release Notes for 5.4|Release Notes 5.4] | *Unreleased* | | || Tapestry 5.3.3 | [Release Notes for 5.3.2|Release Notes 5.3.2] | *Vote Underway* | 17 Apr 2012 | || Tapestry 5.3.2 | [Release Notes for 5.3.2|Release Notes 5.3.2] | *Current stable release* | 07 Feb 2012 | || Tapestry 5.3.1 | [Release Notes for 5.3.1|Release Notes 5.3.1] | | 21 Dec 2011 ... Full Content These release notes provide the details of the changes in each Tapestry version. Be sure to read How to Upgrade too. Tapestry 5.4 Release Notes for 5.4 Unreleased Tapestry 5.3.3 Release Notes for 5.3.2 Vote Underway 17 Apr 2012 Tapestry 5.3.2 Release Notes for 5.3.2 Current stable release 07 Feb 2012 Tapestry 5.3.1 Release Notes for 5.3.1 21 Dec 2011 Tapestry 5.3 Release Notes for 5.3 21 Nov 2011 Tapestry 5.2.6 Release Notes for 5.2.6 Released 22 Jun 2011 Tapestry 5.1 Release Notes for 5.1.0.5 Released 12 Apr 2009 Tapestry 5.0 Release Notes for 5.0.19 Released Dec 2008 Change Notification Preferences View Online | View Changes
[CONF] Apache Tapestry > Release Notes 5.3.3
Release Notes 5.3.3
Page edited by Howard M. Lewis Ship
Changes (2)
{scrollbar}
This is the consolidated list of changes between Tapestry versions 5.3.2 and 5.3.3. Tapestry 5.3.2 is a drop-in replacement for Tapestry 5.3.2. To upgrade, just update the Maven dependency in you POM file (or [download|Download] the new JAR file) and the new version will just work. However, please review the [How to Upgrade] instructions before upgrading. And be sure to check the [Release Notes for 5.3|Release Notes 5.3] too. This is a very modest bug fix release, but it does straighten out a significant problem with Java component classes containing non-private fields. For those developers not using Maven or Gradle, you'll be pleased to know that this release now includes the option of a binary download containing Tapestry's modules and main dependencies. More details are on the [Download] page. h2. Jira issues {html} Release Notes - Tapestry 5 - Version 5.3.3 Bug [ [ [ [ [ [ [ [ Improvement [ New Feature [ Task [ [ {html} {scrollbar}
Full Content
Release Notes 5.4 Release Notes
This is the consolidated list of changes between Tapestry versions 5.3.2 and 5.3.3. Tapestry 5.3.2 is a drop-in replacement for Tapestry 5.3.2. To upgrade, just update the Maven dependency in you POM file (or download the new JAR file) and the new version will just work. However, please review the How to Upgrade instructions before upgrading. And be sure to check the Release Notes for 5.3 too.
This is a very modest bug fix release, but it does straighten out a significant problem with Java component classes containing non-private fields.
For those developers not using Maven or Gradle, you'll be pleased to know that this release now includes the option of a binary download containing Tapestry's modules and main dependencies. More details are on the Download page.
Jira issues
Release Notes - Tapestry 5 - Version 5.3.3
Bug
[TAP5-1791] - On some JDKs, the complex regular _expression_ used by ComponentEventLinkEncoderImpl will cause a stack overflow
[TAP5-1836] - "LocalhostOnly" WhitelistAnalyzer check "0:0:0:0:0:0:0:1%0" ip address instead "0:0:0:0:0:0:0:1"
[TAP5-1844] - Datefield not fires onchange event on changes
[TAP5-1854] - AjaxComponentEventRequestHandler doesn't handle the case where a response has already be returned, and may append an empty JSON Object to the response
[TAP5-1860] - Access to protected component fields does not always reflect in subclasses
[TAP5-1881] - TypeCoercion from Number to Boolean returns false for any number that is an even multiple of 256
[TAP5-1895] - ValidationDecorator.insideLabel(...) is called after the removal of PropertyContext in PropertyEditor
[TAP5-1906] - Interaction between client-side validation and submit buttons can result in a server-side error parsing JSON array
Improvement
[TAP5-1827] - KaptchaField should have a parameter to allow it to operate as a visible text field rather than a password field
New Feature
[TAP5-1857] - Add a SubmitMode (for Submit and LinkSubmit components) for unconditionally submitting the form
Task
[TAP5-1790] - Update Tapestry build to create a binary release archive (in addition to a source and javadoc archive)
[TAP5-1909] - Update Underscore _javascript_ library to latest version 1.3.3
Release Notes 5.4 Release Notes
Change Notification Preferences
View Online
|
View Changes
[CONF] Apache Tapestry > Release Notes 5.3.3
Release Notes 5.3.3 Page added by Howard M. Lewis Ship Change Notification Preferences View Online
[CONF] Apache Tapestry > Release Notes
Release Notes Page edited by Massimo Lusetti Changes (1) ... || Tapestry 5.4 | [Release Notes for 5.4|Release Notes 5.4] | *Unreleased* | | || Tapestry 5.3.2 | [Release Notes for 5.3.2|Release Notes 5.3.2] | *Unreleased* *Currently under vote* | | || Tapestry 5.3.1 | [Release Notes for 5.3.1|Release Notes 5.3.1] |*Current stable release* | 21 Dec 2011 || Tapestry 5.3 | [Release Notes for 5.3|Release Notes 5.3] | | 21 Nov 2011 ... Full Content These release notes provide the details of the changes in each Tapestry version. Be sure to read How to Upgrade too. Tapestry 5.4 Release Notes for 5.4 Unreleased Tapestry 5.3.2 Release Notes for 5.3.2 Currently under vote Tapestry 5.3.1 Release Notes for 5.3.1 Current stable release 21 Dec 2011 Tapestry 5.3 Release Notes for 5.3 21 Nov 2011 Tapestry 5.2.6 Release Notes for 5.2.6 Released 22 Jun 2011 Tapestry 5.1 Release Notes for 5.1.0.5 Released 12 Apr 2009 Tapestry 5.0 Release Notes for 5.0.19 Released Dec 2008 Change Notification Preferences View Online | View Changes
[CONF] Apache Tapestry > Release Notes 5.3.2
Release Notes 5.3.2
Page edited by Massimo Lusetti
Changes (2)
{scrollbar}
This is the consolidated list of changes between Tapestry versions 5.3.1 and 5.3.2. To upgrade, just update the Maven dependency in you POM file (or [download|Download] the new JAR file) and the new version will just work. However, please review the [How to Upgrade] instructions before upgrading. And be sure to check the [Release Notes for 5.3|Release Notes 5.3] and [Release Notes for 5.3.1|Release Notes 5.3.1] too.
h2. New Features
...
In prior versions of Tapestry, all instance fields of components had to be visibility private; starting with version 5.3.2, this has been relaxed. Component fields may be protected, or package private (that is, no visibility modifier). Fields that are final, or annotated with @[Retain|http://tapestry.apache.org/current/apidocs/org/apache/tapestry5/annotations/Retain.html] may even be public. In any case, this makes it easier for pages to work with other pages in the same package, and for subclasses to more easily access the fields (including parameter fields, or injections) provided by base classes. This feature should be used with care, as it can lead to designs that are more difficult to maintain.
h3. Spring 3.1 upgrade The Spring integration module has updated the Spring dependencies to 3.1.0.RELEASE h4. TextField component support for HTML5 values The [TextField|http://tapestry.apache.org/current/apidocs/org/apache/tapestry5/corelib/components/TextField.html] components now support HTML5 any HTML5 type attribute. h2. Jira issues {html} Release Notes - Tapestry 5 - Version 5.3.2 Bug [ [ [ [ Improvement [ [ Task [ {html}
{scrollbar}
Full Content
Release Notes 5.3.1 Release Notes Release Notes 5.4
This is the consolidated list of changes between Tapestry versions 5.3.1 and 5.3.2. To upgrade, just update the Maven dependency in you POM file (or download the new JAR file) and the new version will just work. However, please review the How to Upgrade instructions before upgrading. And be sure to check the Release Notes for 5.3 and Release Notes for 5.3.1 too.
New Features
Component field visibility
In prior versions of Tapestry, all instance fields of components had to be visibility private; starting with version 5.3.2, this has been relaxed. Component fields may be protected, or package private (that is, no visibility modifier). Fields that are final, or annotated with @Retain may even be public. In any case, this makes it easier for pages to work with other pages in the same package, and for subclasses to more easily access the fields (including parameter fields, or injections) provided by base classes. This feature should be used with care, as it can lead to designs that are more difficult to maintain.
Spring 3.1 upgrade
The Spring integration module has updated the Spring dependencies to 3.1.0.RELEASE
TextField component support for HTML5 values
The TextField components now support HTML5 any HTML5 type attribute.
Jira issues
Release Notes - Tapestry 5 - Version 5.3.2
Bug
[TAP5-1787] - TextField should be usable with HTML5 type values (such as "number", "email", etc.)
[TAP5-1788] - Service id 'environment' has already been defined by org.apache.tapestry5.services.TapestryModule with Spring 3.1
[TAP5-1798] - Grid and BeanDisplay should ignore properties that are actually static fields
[TAP5-1825] - Incorrect order of parameter in localization messages within ValidationMessages Italian lang
Improvement
[TAP5-1801] - Component fields should not need to be private, merely non-public
[TAP5-1824] - New translations for Norwegian Bokmål
Task
[TAP5-1792] - Upgrade Tapestry/Spring integration to Spring 3.1.0.RELEASE
Release Notes 5.3.1 Release Notes Release Notes 5.4
Change Notification Preferences
View Online
|
View Changes
[CONF] Apache Tapestry > Release Notes 5.3.2
Release Notes 5.3.2 Page moved by Bob Harner From: Apache Tapestry > Release Notes 5.3 To: Apache Tapestry > Release Notes Children moved Change Notification Preferences View Online
[CONF] Apache Tapestry > Release Notes 5.3.1
Release Notes 5.3.1 Page moved by Bob Harner From: Apache Tapestry > Release Notes 5.3 To: Apache Tapestry > Release Notes Children moved Change Notification Preferences View Online
[CONF] Apache Tapestry > Release Notes 5.3.2
Release Notes 5.3.2 Page moved by Bob Harner From: Apache Tapestry > Release Notes To: Apache Tapestry > Release Notes 5.3 Children moved Change Notification Preferences View Online
[CONF] Apache Tapestry > Release Notes
Release Notes Page edited by Bob Harner Comment: Added link to new How to Upgrade page Changes (1) These release notes provide the details of the changes in each Tapestry version. Be sure to read [How to Upgrade] too. || Tapestry 5.4 | [Release Notes for 5.4|Release Notes 5.4] | *Unreleased* | | ... Full Content These release notes provide the details of the changes in each Tapestry version. Be sure to read How to Upgrade too. Tapestry 5.4 Release Notes for 5.4 Unreleased Tapestry 5.3.2 Release Notes for 5.3.2 Unreleased Tapestry 5.3.1 Release Notes for 5.3.1 Current stable release 21 Dec 2011 Tapestry 5.3 Release Notes for 5.3 21 Nov 2011 Tapestry 5.2.6 Release Notes for 5.2.6 Released 22 Jun 2011 Tapestry 5.1 Release Notes for 5.1.0.5 Released 12 Apr 2009 Tapestry 5.0 Release Notes for 5.0.19 Released Dec 2008 Change Notification Preferences View Online | View Changes
[CONF] Apache Tapestry > Release Notes for 5.3.2
Release Notes for 5.3.2 Page added by Bob Harner This page has moved to Release Notes 5.3.2 Change Notification Preferences View Online
[CONF] Apache Tapestry > Release Notes 5.3.2
Release Notes 5.3.2
Page edited by Bob Harner
Comment:
Changed page name for consistency
Changes (1)
{scrollbar}
This is the consolidated list of changes between Tapestry versions 5.3.1 and 5.3.2. To upgradem, just update the Maven dependency in you POM file (or [download|Download] the new JAR file) and the new version will just work. However, please read carefully below before upgrading. And be sure to check the [Release Notes for 5.3|Release Notes 5.3] too.
h2. New Features
...
Full Content
Release Notes 5.4 Release Notes
This is the consolidated list of changes between Tapestry versions 5.3.1 and 5.3.2. To upgrade, just update the Maven dependency in you POM file (or download the new JAR file) and the new version will just work. However, please read carefully below before upgrading. And be sure to check the Release Notes for 5.3 too.
New Features
Component field visibility
In prior versions of Tapestry, all instance fields of components had to be visibility private; starting with version 5.3.2, this has been relaxed. Component fields may be protected, or package private (that is, no visibility modifier). Fields that are final, or annotated with @Retain may even be public. In any case, this makes it easier for pages to work with other pages in the same package, and for subclasses to more easily access the fields (including parameter fields, or injections) provided by base classes. This feature should be used with care, as it can lead to designs that are more difficult to maintain.
Release Notes 5.4 Release Notes
Change Notification Preferences
View Online
|
View Changes
[CONF] Apache Tapestry > Release Notes 5.4
Release Notes 5.4
Page edited by Howard M. Lewis Ship
Changes (1)
{scrollbar}
This is the consolidated list of changes between Tapestry versions 5.3 and 5.4. To upgrade from 5.2 to 5.34, most users who are not using deprecated features will be able to just update the Maven dependency in their POM file (or [download|Download] the new JAR file) and the new version will just work. However, please read carefully below before upgrading.
h2. Breaking Features
...
Full Content
Release Notes 5.3 Release Notes Release Notes for 5.3.2
This is the consolidated list of changes between Tapestry versions 5.3 and 5.4. To upgrade to 5.4, most users who are not using deprecated features will be able to just update the Maven dependency in their POM file (or download the new JAR file) and the new version will just work. However, please read carefully below before upgrading.
Breaking Features
Tapestry's use of the Javassist bytecode library has been completely removed, along with many related services, such as ClassFactory, that were deprecated in 5.3. Use PlasticProxyFactory instead.
No Redirect On Form Validation Errors
In prior releases of Tapestry, when a client-side form was submitted and there were server-side validation errors, Tapestry would perform a redirect-after-post to re-render the page; this meant that the ValidationTracker object that stores validation errors would, itself, need to persist to the new render request, causing a server-side session to be created. Starting in 5.4, the default behavior for server-side validation exceptions is to re-render the page within the same request; this obviates the need to use a persistent field to store the tracker.
New Features
Component field visibility
In prior versions of Tapestry, all instance fields of components had to be visibility private; starting with versions 5.3.2 and 5.4, this has been relaxed. Component fields may be protected, or package private (that is, no visibility modifier). Fields that are final, or annotated with @Retain may even be public. In any case, this makes it easier for pages to work with other pages in the same package, and for subclasses to more easily access the fields (including parameter fields, or injections) provided by base classes. This feature should be used with care, as it can lead to designs that are more difficult to maintain.
Release Notes 5.3 Release Notes Release Notes for 5.3.2
Change Notification Preferences
View Online
|
View Changes
[CONF] Apache Tapestry > Release Notes
Release Notes Page edited by Howard M. Lewis Ship Changes (1) These release notes provide the details of the changes in each Tapestry version. || Tapestry 5.3.1 | [Release Notes for 5.4|Release Notes 5.4] | *Unreleased* | | || Tapestry 5.3.1 | [Release Notes for 5.3.2|Release Notes 5.3.2] | *Unreleased* | | || Tapestry 5.3.1 | [Release Notes for 5.3.1|Release Notes 5.3.1] |*Current stable release* | 21 Dec 2011 || Tapestry 5.3 | [Release Notes for 5.3|Release Notes 5.3] | | 21 Nov 2011 ... Full Content These release notes provide the details of the changes in each Tapestry version. Tapestry 5.3.1 Release Notes for 5.4 Unreleased Tapestry 5.3.1 Release Notes for 5.3.2 Unreleased Tapestry 5.3.1 Release Notes for 5.3.1 Current stable release 21 Dec 2011 Tapestry 5.3 Release Notes for 5.3 21 Nov 2011 Tapestry 5.2.6 Release Notes for 5.2.6 Released 22 Jun 2011 Tapestry 5.1 Release Notes for 5.1.0.5 Released 12 Apr 2009 Tapestry 5.0 Release Notes for 5.0.19 Released Dec 2008 Change Notification Preferences View Online | View Changes
[CONF] Apache Tapestry > Release Notes for 5.3.2
Release Notes for 5.3.2 Page added by Howard M. Lewis Ship Release Notes This is the consolidated list of changes between Tapestry versions 5.3.1 and 5.3.2. To upgradem just update the Maven dependency in you POM file (or download the new JAR file) and the new version will just work. However, please read carefully below before upgrading. New Features Component field visibility In prior versions of Tapestry, all instance fields of components had to be visibility private; starting with version 5.3.2, this has been relaxed. Component fields may be protected, or package private (that is, no visibility modifier). Fields that are final, or annotated with @Retain may even be public. In any case, this makes it easier for pages to work with other pages in the same package, and for subclasses to more easily access the fields (including parameter fields, or injections) provided by base classes. This feature should be used with care, as it can lead to designs that are more difficult to maintain. Release Notes Change Notification Preferences View Online
[CONF] Apache Tapestry > Release Notes 5.4
Release Notes 5.4
Page edited by Howard M. Lewis Ship
Changes (1)
...
In prior versions of Tapestry, all instance fields of components had to be visibility private; starting with versions 5.3.2 and 5.4, this has been relaxed. Component fields may be protected, or package private (that is, no visibility modifier). Fields that are final, or annotated with ![Retain|http://tapestry.apache.org/current/apidocs/org/apache/tapestry5/annotations/Retain.html] may even be public. In any case, this makes it easier for pages to work with other pages in the same package, and for subclasses to more easily access the fields (including parameter fields, or injections) provided by base classes. This feature should be used with care, as it can lead to designs that are more difficult to maintain.
{scrollbar}
Full Content
Release Notes 5.3 Release Notes
This is the consolidated list of changes between Tapestry versions 5.3 and 5.4. To upgrade from 5.2 to 5.3, most users who are not using deprecated features will be able to just update the Maven dependency in their POM file (or download the new JAR file) and the new version will just work. However, please read carefully below before upgrading.
Breaking Features
Tapestry's use of the Javassist bytecode library has been completely removed, along with many related services, such as ClassFactory, that were deprecated in 5.3. Use PlasticProxyFactory instead.
New Features
Component field visibility
In prior versions of Tapestry, all instance fields of components had to be visibility private; starting with versions 5.3.2 and 5.4, this has been relaxed. Component fields may be protected, or package private (that is, no visibility modifier). Fields that are final, or annotated with !Retain may even be public. In any case, this makes it easier for pages to work with other pages in the same package, and for subclasses to more easily access the fields (including parameter fields, or injections) provided by base classes. This feature should be used with care, as it can lead to designs that are more difficult to maintain.
Release Notes 5.3 Release Notes
Change Notification Preferences
View Online
|
View Changes
[CONF] Apache Tapestry > Release Notes 5.4
Release Notes 5.4 Page added by Howard M. Lewis Ship Release Notes This is the consolidated list of changes between Tapestry versions 5.3 and 5.4. To upgrade from 5.2 to 5.3, most users who are not using deprecated features will be able to just update the Maven dependency in their POM file (or download the new JAR file) and the new version will just work. However, please read carefully below before upgrading. Breaking Features Tapestry's use of the Javassist bytecode library has been completely removed, along with many related services, such as ClassFactory, that were deprecated in 5.3. Use PlasticProxyFactory instead. New Features Component field visibility In prior versions of Tapestry, all instance fields of components had to be visibility private; starting with versions 5.3.2 and 5.4, this has been relaxed. Component fields may be protected, or package private (that is, no visibility modifier). Fields that are final, or annotated with !Retain may even be public. In any case, this makes it easier for pages to work with other pages in the same package, and for subclasses to more easily access the fields (including parameter fields, or injections) provided by base classes. This feature should be used with care, as it can lead to designs that are more difficult to maintain. Change Notification Preferences View Online
[CONF] Apache Tapestry > Release Notes 5.3.1
Release Notes 5.3.1
Page edited by Howard M. Lewis Ship
Changes (3)
{scrollbar}
This bugfix release is a drop -in replacement for the [5.3|Release Notes 5.3] release. Any 5.3 user is encoraged to upgrade.
The release is undergoing a VOTE right now, as the VOTE ends this page will reflect the results.
h2. JIRA Issues
...
[have include a description of their parameters in their JavaDoc pages
[
...
Full Content
Release Notes 5.3
This bugfix release is a drop-in replacement for the 5.3 release. Any 5.3 user is encoraged to upgrade.
JIRA Issues
Release Notes - Tapestry 5 - Version 5.3.1
Bug
[TAP5-1762] - Some components do not include a description of their parameters in their JavaDoc pages
[TAP5-1765] - PerThread scope is not honored when service is created using autobuild
[TAP5-1768] - @ActivationRequestParameter does not encode to be URL friendly
[TAP5-1773] - FormFieldFocus mixin passes control name, not client id, to _javascript_Support.autofocus()
[TAP5-1784] - Extra comma in tapestry-messages_de.js causes Internet Explorer to fail to work
[TAP5-1785] - Exceptions while compressing _javascript_ are not fully reported
[TAP5-1786] - All forms/submission not working after FileUploadException is raised
Improvement
[TAP5-1756] - Let the asset path prefix be configurable
Task
[TAP5-1780] - Upgrade Selenium dependency to 2.14.0
Release Notes 5.3
Change Notification Preferences
View Online
|
View Changes
[CONF] Apache Tapestry > Release Notes
Release Notes Page edited by Howard M. Lewis Ship Changes (2) These release notes provide the details of the changes in each Tapestry version. || Tapestry 5.3.1 | [Release Notes for 5.3.1|Release Notes 5.3.1] |*Current stable release* | *Currently undergoing a vote* | 14 21 Dec 2011 || Tapestry 5.3 | [Release Notes for 5.3|Release Notes 5.3] | *Current stable release* | 21 Nov 2011 || Tapestry 5.2.6 | [Release Notes for 5.2.6|Release Notes 5.2] | | Released 22 Jun 2011 | || Tapestry 5.1| [Release Notes for 5.1.0.5|Release Notes 5.1] | | Released 12 Apr 2009 | ... Full Content These release notes provide the details of the changes in each Tapestry version. Tapestry 5.3.1 Release Notes for 5.3.1 Current stable release 21 Dec 2011 Tapestry 5.3 Release Notes for 5.3 21 Nov 2011 Tapestry 5.2.6 Release Notes for 5.2.6 Released 22 Jun 2011 Tapestry 5.1 Release Notes for 5.1.0.5 Released 12 Apr 2009 Tapestry 5.0 Release Notes for 5.0.19 Released Dec 2008 Change Notification Preferences View Online | View Changes
[CONF] Apache Tapestry > Release Notes 5.3.1
Release Notes 5.3.1 Page moved by Massimo Lusetti From: Apache Tapestry > Release Notes To: Apache Tapestry > Release Notes 5.3 Children moved Change Notification Preferences View Online
[CONF] Apache Tapestry > Release Notes
Release Notes Page edited by Massimo Lusetti Changes (1) These release notes provide the details of the changes in each Tapestry version. || Tapestry 5.3.1 | [Release Notes for 5.3.1|Release Notes 5.3.1] | *Currently undergoing a vote* | 154 Dec 2011 || Tapestry 5.3 | [Release Notes for 5.3|Release Notes 5.3] | *Current stable release* | 21 Nov 2011 || Tapestry 5.2.6 | [Release Notes for 5.2.6|Release Notes 5.2] | | Released 22 Jun 2011 | ... Full Content These release notes provide the details of the changes in each Tapestry version. Tapestry 5.3.1 Release Notes for 5.3.1 Currently undergoing a vote 14 Dec 2011 Tapestry 5.3 Release Notes for 5.3 Current stable release 21 Nov 2011 Tapestry 5.2.6 Release Notes for 5.2.6 Released 22 Jun 2011 Tapestry 5.1 Release Notes for 5.1.0.5 Released 12 Apr 2009 Tapestry 5.0 Release Notes for 5.0.19 Released Dec 2008 Change Notification Preferences View Online | View Changes
[CONF] Apache Tapestry > Release Notes
Release Notes Page edited by Massimo Lusetti Changes (1) These release notes provide the details of the changes in each Tapestry version. || Tapestry 5.3.1 | [Release Notes for 5.3.1|Release Notes 5.3.1] | *Currently undergoing a vote* | 15 Dec 2011 || Tapestry 5.3 | [Release Notes for 5.3|Release Notes 5.3] | *Current stable release* | 21 Nov 2011 || Tapestry 5.2.6 | [Release Notes for 5.2.6|Release Notes 5.2] | | Released 22 Jun 2011 | ... Full Content These release notes provide the details of the changes in each Tapestry version. Tapestry 5.3.1 Release Notes for 5.3.1 Currently undergoing a vote 15 Dec 2011 Tapestry 5.3 Release Notes for 5.3 Current stable release 21 Nov 2011 Tapestry 5.2.6 Release Notes for 5.2.6 Released 22 Jun 2011 Tapestry 5.1 Release Notes for 5.1.0.5 Released 12 Apr 2009 Tapestry 5.0 Release Notes for 5.0.19 Released Dec 2008 Change Notification Preferences View Online | View Changes
[CONF] Apache Tapestry > Release Notes 5.3.1
Release Notes 5.3.1 Page added by Massimo Lusetti Release Notes This bugfix release is a drop in replacement for the 5.3 release. Any 5.3 user is encoraged to upgrade. The release is undergoing a VOTE right now, as the VOTE ends this page will reflect the results. JIRA Issues Release Notes - Tapestry 5 - Version 5.3.1 Bug [TAP5-1762] - Some components do not have include a description of their parameters in their JavaDoc pages [TAP5-1765] - PerThread scope is not honored when service is created using autobuild [TAP5-1768] - @ActivationRequestParameter does not encode to be URL friendly [TAP5-1773] - FormFieldFocus mixin passes control name, not client id, to _javascript_Support.autofocus() [TAP5-1784] - Extra comma in tapestry-messages_de.js causes Internet Explorer to fail to work [TAP5-1785] - Exceptions while compressing _javascript_ are not fully reported [TAP5-1786] - All forms/submission not working after FileUploadException is raised Improvement [TAP5-1756] - Let the asset path prefix be configurable Task [TAP5-1780] - Upgrade Selenium dependency to 2.14.0 Release Notes Change Notification Preferences View Online
[CONF] Apache Tapestry > Release Notes
Release Notes Page edited by Howard M. Lewis Ship Changes (5) These release notes provide the details of the changes in each Tapestry version. || Tapestry 5.3 | [Release Notes for 5.3|Release Notes 5.3] | _Current release candidate_ *Current stable release* | 21 Nov 2011 || Tapestry 5.2 | [Consolidated Release Notes for 5.2|Release Notes 5.2] | *This is the current stable release* | || | [Release Notes 5.2.5] | Released 23 Mar 2011 | || | [Release Notes 5.2.4] | Released 15 Nov 2010 | || | [Release Notes 5.2.3] | Released 11 Nov 2010 | || | [Release Notes 5.2.2] | Released 24 Oct 2010 | || | [Release Notes 5.2.1] | Released 29 Sep 2010 | || | [Release Notes 5.2.0] | Released 8 Aug 2010 | || Tapestry 5.2.6 | [Release Notes for 5.2.6|Release Notes 5.2] | | Released 22 Jun 2011 | || Tapestry 5.1| [Release Notes for 5.1.0.5|Release Notes 5.1] | | Released 12 Apr 2009 | || Tapestry 5.0| [Release Notes for 5.0.19|Release Notes 5.0] | | Released Dec 2008 | Full Content These release notes provide the details of the changes in each Tapestry version. Tapestry 5.3 Release Notes for 5.3 Current stable release 21 Nov 2011 Tapestry 5.2.6 Release Notes for 5.2.6 Released 22 Jun 2011 Tapestry 5.1 Release Notes for 5.1.0.5 Released 12 Apr 2009 Tapestry 5.0 Release Notes for 5.0.19 Released Dec 2008 Change Notification Preferences View Online | View Changes
[CONF] Apache Tapestry > Release Notes
Release Notes Page edited by Howard M. Lewis Ship Changes (1) These release notes provide the details of the changes in each Tapestry version. || Tapestry 5.3 | [Consolidated Release Notes for 5.3|Release Notes 5.3] | _Current release candidate_ | || Tapestry 5.2 | [Consolidated Release Notes for 5.2|Release Notes 5.2] | *This is the current stable release* | || | [Release Notes 5.2.5] | Released 23 Mar 2011 | ... Full Content These release notes provide the details of the changes in each Tapestry version. Tapestry 5.3 Release Notes for 5.3 Current release candidate Tapestry 5.2 Consolidated Release Notes for 5.2 This is the current stable release Release Notes 5.2.5 Released 23 Mar 2011 Release Notes 5.2.4 Released 15 Nov 2010 Release Notes 5.2.3 Released 11 Nov 2010 Release Notes 5.2.2 Released 24 Oct 2010 Release Notes 5.2.1 Released 29 Sep 2010 Release Notes 5.2.0 Released 8 Aug 2010 Tapestry 5.1 Release Notes 5.1 Released 12Apr 2009 Tapestry 5.0 Release Notes 5.0 Released Dec 2008 Change Notification Preferences View Online | View Changes
[CONF] Apache Tapestry > Release Notes 5.3.0
Release Notes 5.3.0 Page removed by Howard M. Lewis Ship Release Note Release Notes - Tapestry 5 - Version 5.3.0 Sub-task [TAP5-1433] - Remove deprecated methods of PerthreadManager service [TAP5-1434] - Remove old IOCSymbols class, and outdated constants from IOCConstants [TAP5-1435] - Remove proxy-related building method from ClassFabUtils, since moved to ClassFactory#createProxy() [TAP5-1436] - Remove @ApplicationState annotation, replaced with @SessionState [TAP5-1437] - Remove @IncludeJavaScriptLibrary and @IncludeStylesheet annotations, replaced by @Import [TAP5-1438] - Remove OptimizedApplicationStateObject, replaced with OptimizedSessionStateObject [TAP5-1439] - Remove PrimaryKeyEncoder (replaced by ValueEncoder) [TAP5-1440] - Remove "validateForm" event triggered by Form component (replaced with "validate" event) [TAP5-1441] - Remove ValidationMessagesSource, replaced with ComponentMessagesSource [TAP5-1455] - Remove code and constants related to page pooling [TAP5-1456] - Remove symbol for absolute URIs (now always absolute since 5.2) [TAP5-1457] - Remove SCRIPTS_AT_TOP from SymbolConstants [TAP5-1459] - Remove AbstractField.createDefaultParameterBinding() and AbstractTextField.defaultValue() [TAP5-1460] - Remove deprecated constants from FormInjector [TAP5-1461] - Remove Loop.volatile parameter (replaced with formState parameter in 5.1) [TAP5-1462] - Remove Element.getParent() [TAP5-1463] - Remove EndTagStyle.OMIT [TAP5-1464] - Remove ClasspathAssetAliasManager.toResourcePath() [TAP5-1465] - Remove Environment.getAccess() [TAP5-1466] - Remove deprecated methods from TapestryTestCase [TAP5-1467] - Remove deprecated methods from ClassTransformation Bug [TAP5-35] - During an Ajax update, using a "var:" binding prefix causes an exception indicating that the page is not rendering [TAP5-763] - Documentation for RenderSupport.addScriptLink() is invalid about where the included links go [TAP5-875] - BigTypesFormatter should allow for plain space as a grouping separator since FF2 replaces non-breaking space character \u00A0 (grouping separator for Sweden, Finland , etc) with normal space \u0020 [TAP5-922] - Allow a null or blank value to be supplied in Link.addParameter(), and render out the parameter name with the missing value [TAP5-998] - Exception when a form element component is not enclosed by a Form is odd: uses the form's label to identify the component in question [TAP5-1146] - In a Multi-Zone update, if the identified Zone does not exist, the content is silently dropped (should log an error to the client-side console) [TAP5-1257] - _javascript_ error with IE Prototype still in 1.7 [TAP5-1372] - BaseURLSource uses getLocalPort() rather than getServerPort() [TAP5-1374] - Quickstart layout component uses deprecated IncludeStyleSheet annotation [TAP5-1383] - TypeCoercer should "promote" coercions to primitive types into coercions to the corresponding wrapper type [TAP5-1393] - Form component shoould push the BeanValidationContext into the Environment only after onPrepare() [TAP5-1418] - Image submits do not set the _javascript_ submitting element value. [TAP5-1422] - java.util.ConcurrentModificationException when shutting down jmx server [TAP5-1429] - PageTester does not call registry.performRegistryStartup or TapestryAppInitializer.announceStartup [TAP5-1444] - Index pages in subfolders should have precedence over start pages [TAP5-1491] - In Chrome the buttons in the Palette component do not appear greyed-out when disabled [TAP5-1510] - The @Advise annotation limits advice to just a specific interface type [TAP5-1527] - BeanEditForm loses object found by onPrepare() during render Improvement [TAP5-98] - The TypeCoercer should be able to coerce String to Enum types, even without a specific contribution [TAP5-683] - The Tapestry object should include an info() for logging to the console (as it already includes error(), debug(), etc.) [TAP5-741] - CSS files should be automatically minimalized, like _javascript_ files [TAP5-853] - Move away from Javassist [TAP5-1040] - Allow HTML5 doctype to be printed [TAP5-1208] - In development mode, Tapestry should "shadow" field & parameter values to instance variables, to assist with debugging [TAP5-1320] - ServiceActivity improvements [TAP5-1323] - Change Quickstart Template to Match New Site Design [TAP5-1348] - Component report should accept multiple root packages [TAP5-1356] - When contri
[CONF] Apache Tapestry > Release Notes 5.3
Release Notes 5.3
Page edited by Bob Harner
Comment:
Corrected the descriptions of Breaking Changes to my understanding
Changes (7)
{scrollbar}
This is the consolidated list of changes between Tapestry versions 5.2 and 5.3. To upgrade from 5.12 to 5.23, most users who are not using deprecated features will be able to just update the Maven dependency in their POM file (or [download|Download] the new JAR file) and the new version will just work. However, please read carefully below before upgrading.
*Contents*
...
h2. Breaking Changes
Some number of interfaces and APIs in Tapestry 5.3 will be removed in Tapestry 5.4 or later. These include: * The "suppress redirects" functionality, which allows component event requests to respond directly with HTML, as in Tapestry 4 * The RenderSupport environmental (replaced with the _javascript_Support environmental) * ClassFactory service and ClassFab interface (replaced with the PlasticProxyFactory service and PlasticClass interface)
Many classes and interfaces that were deprecated in prior releases of Tapestry have been removed in Tapestry 5.3. See [the full list|https://issues.apache.org/jira/browse/TAP5-1432]. As always, you should use your IDE to find and replace all deprecated items _before_ you upgrade. The following are the most significant of these:
Many classes and interfaces marked as deprecated in prior releases of Tapestry have been removed.
* @IncludeJavaScriptLibrary and @IncludeStylesheet annotations (replaced by @Import) * @ApplicationState annotation (replaced with @SessionState) * "validateForm" event triggered by Form component (replaced with "validate" event) * Code and constants related to page pooling * The "suppress redirects" functionality, which allows component event requests to respond directly with HTML, as in Tapestry 4.
Because of the upgrade to Prototype 1.7, existing _javascript_ that uses {{value.toJSON()}} may break; replace with {{Object.toJSON(value)}}.
Some number of interfaces and APIs in Tapestry 5.3 will be removed in Tapestry 5.4 or later. These include: * The RenderSupport environmental (replaced with the _javascript_Support environmental) * ClassFactory service and ClassFab interface (replaced with the PlasticProxyFactory service and PlasticClass interface)
h2. New Features
...
h3. Component debugging improvements
Because of how Tapestry instruments your pages and components, it using a debugger has been difficult to debug with Tapestry applications; page and component classes; any mutable field shows its default value in the debugger, regardless of what has been written to the field or read out of it. In Tapestry 5.3, when in _development mode_, Tapestry now shadows values read from or written to such fields into the fields themselves (this has also been fixed in the 5.2.5 maintenance release). This shadowing does not occur in production, to avoid potential memory leaks.
h3. Reloading disabled in production
...
Full Content
Release Notes 5.2 Release Notes
This is the consolidated list of changes between Tapestry versions 5.2 and 5.3. To upgrade from 5.2 to 5.3, most users who are not using deprecated features will be able to just update the Maven dependency in their POM file (or download the new JAR file) and the new version will just work. However, please read carefully below before upgrading.
Contents
Breaking Changes
New Features
Removed Functionality
Release Notes: Tapestry 5.3.0
Sub-task
Bug
Improvement
New Feature
Task
Test
Breaking Changes
Many classes and interfaces that were deprecated in prior releases of Tapestry have been removed in Tapestry 5.3. See the full list. As always, you should use your IDE to find and replace all deprecated items before you upgrade. The following are the most significant of these:
@IncludeJavaScriptLibrary and @IncludeStylesheet annotations (replaced by @Import)
@ApplicationState annotation (replaced with @SessionState)
"validateForm" event triggered by Form component (replaced with "validate" event)
Code and constants related to page pooling
The "suppress redirects" functionality, which allows component event requests to respond directly with HTML, as in Tapestry 4.
Because of the upgrade to Prototype 1.7, existing _javascript_ that uses value.toJSON() may break; replace with Object.toJSON(value).
Some number of interfaces and APIs in Tapestry 5.3 will be removed in Tapestry 5.4 or later. These include:
The RenderSupport environmental (replaced with
[CONF] Apache Tapestry > Release Notes 5.3
Release Notes 5.3
Page edited by Howard M. Lewis Ship
Comment:
add note about application folders
Changes (2)
...
h3. New Component Class Validations
Tapestry includes new validations of component classes to help cut down on many common errors; Tapestry now checks that component ids referencesd by an event handler method (the {{From}}_component id_ part of the method name) actually matches a component defined in the template ... this quickly identifies typos in method names. This check can be disabled with a configuration symbol, as existing 5.2 apps may have such errors and still operate (that is, they may have _dead_ event handler methods that will never be invoked).
h3. Application Folder Tapestry can now be configured to execute inside a folder, which can be useful when running Tapestry inside a web application that contains other servlet or filters, as a way to prevent conflicts.
h2. Removed Functionality
...
Full Content
Release Notes 5.2 Release Notes
This is the consolidated list of changes between Tapestry versions 5.2 and 5.3. To upgrade from 5.1 to 5.2, most users will be able to just update the Maven dependency in their POM file (or download the new JAR file) and the new version will just work. However, please read carefully below before upgrading.
Contents
Breaking Changes
New Features
Removed Functionality
Release Notes: Tapestry 5.3.0
Sub-task
Bug
Improvement
New Feature
Task
Test
Breaking Changes
Some number of interfaces and APIs in Tapestry 5.3 will be removed in Tapestry 5.4 or later. These include:
The "suppress redirects" functionality, which allows component event requests to respond directly with HTML, as in Tapestry 4
The RenderSupport environmental (replaced with the _javascript_Support environmental)
ClassFactory service and ClassFab interface (replaced with the PlasticProxyFactory service and PlasticClass interface)
Many classes and interfaces marked as deprecated in prior releases of Tapestry have been removed.
Because of the upgrade to Prototype 1.7, existing _javascript_ that uses value.toJSON() may break; replace with Object.toJSON(value).
New Features
User Alerts
Tapestry now has a central mechanism for handling user alerts; this includes the AlertManager service and the Alerts component. Just add an Alerts component to your application's standard layout component and Tapestry takes care of the rest. Alerts can be added during both traditional and Ajax requests, and may be transient (displayed for a few seconds), normal, or sticky (persist until the user expressly dismisses them). Alerts support three severities: info, warn(ing) and error; the look and feel can be customized by overriding Tapestry's default CSS rules.
Rendering comments
It is now possible to have Tapestry emit rendering comments; these are comments (such as ) that can assist you in debugging markup output on the client-side. This is enabled for all requests using the configuration symbol tapestry.component-render-tracing-enabled, and can be added to any request by adding the query parameter t:component-trace=true to the URL. This will significantly increase the size of the rendered markup, but can be very helpful with complex layouts to determine which component was responsible for which portion of the rendered page.
Adaptable service contributions
When making contributions to a service, you are no longer restricted to contributing a value that is assignable to the type associated with the configuration; objects of any type may be contributed, and the TypeCoercer service is used to coerce the value to the configuration's type.
Component debugging improvements
Because of how Tapestry instruments your pages and components, it has been difficult to debug Tapestry applications; any mutable field shows its default value in the debugger, regardless of what has been written to the field or read out of it. In Tapestry 5.3, when in development mode, Tapestry now shadows values read from or written to such fields into the fields themselves (this has also been fixed in the 5.2.5 maintenance release). This does not occur in production, to avoid potential memory leaks.
Reloading disabled in production
Tapestry no longer checks for changes to Tapestry component class files, templates, or message catalogs in production mode. It is assumed that Tapestry applications are packaged as WAR files in production, and that changing the WAR file causes the servlet container to redeploy the entire application. This change is to improve throughput and reduce memory consumption in production applications.
String-to-Enum coercions
The T
[CONF] Apache Tapestry > Release Notes 5.3
Release Notes 5.3
Page edited by Howard M. Lewis Ship
Comment:
mention the new user alerts system, and new component class validations
Changes (3)
...
h2. New Features
h3. User Alerts Tapestry now has a central mechanism for handling user alerts; this includes the AlertManager service and the Alerts component. Just add an Alerts component to your application's standard layout component and Tapestry takes care of the rest. Alerts can be added during both traditional and Ajax requests, and may be transient (displayed for a few seconds), normal, or sticky (persist until the user expressly dismisses them). Alerts support three severities: info, warn(ing) and error; the look and feel can be customized by overriding Tapestry's default CSS rules.
h3. Rendering comments
...
When using {{OrderedConfiguration.add()}} with no constraints, Tapestry will now implicitly order the added element after the previously added element, within the same method. In prior releases, such elements were added with no constraints. This makes it easier to contribute a group of related items with an implicit ordering.
h3. New Component Class Validations
Tapestry includes new validations of component classes to help cut down on many common errors; Tapestry now checks that component ids references by an event handler method (the {{From}}_component id_ part of the method name) actually matches a component defined in the template ... this quickly identifies typos in method names. This check can be disabled with a configuration symbol, as existing 5.2 apps may have such errors and still operate (that is, they may have _dead_ event handler methods that will never be invoked).
h2. Removed Functionality
...
Full Content
Release Notes 5.2 Release Notes
This is the consolidated list of changes between Tapestry versions 5.2 and 5.3. To upgrade from 5.1 to 5.2, most users will be able to just update the Maven dependency in their POM file (or download the new JAR file) and the new version will just work. However, please read carefully below before upgrading.
Contents
Breaking Changes
New Features
Removed Functionality
Release Notes: Tapestry 5.3.0
Sub-task
Bug
Improvement
New Feature
Task
Test
Breaking Changes
Some number of interfaces and APIs in Tapestry 5.3 will be removed in Tapestry 5.4 or later. These include:
The "suppress redirects" functionality, which allows component event requests to respond directly with HTML, as in Tapestry 4
The RenderSupport environmental (replaced with the _javascript_Support environmental)
ClassFactory service and ClassFab interface (replaced with the PlasticProxyFactory service and PlasticClass interface)
Many classes and interfaces marked as deprecated in prior releases of Tapestry have been removed.
Because of the upgrade to Prototype 1.7, existing _javascript_ that uses value.toJSON() may break; replace with Object.toJSON(value).
New Features
User Alerts
Tapestry now has a central mechanism for handling user alerts; this includes the AlertManager service and the Alerts component. Just add an Alerts component to your application's standard layout component and Tapestry takes care of the rest. Alerts can be added during both traditional and Ajax requests, and may be transient (displayed for a few seconds), normal, or sticky (persist until the user expressly dismisses them). Alerts support three severities: info, warn(ing) and error; the look and feel can be customized by overriding Tapestry's default CSS rules.
Rendering comments
It is now possible to have Tapestry emit rendering comments; these are comments (such as ) that can assist you in debugging markup output on the client-side. This is enabled for all requests using the configuration symbol tapestry.component-render-tracing-enabled, and can be added to any request by adding the query parameter t:component-trace=true to the URL. This will significantly increase the size of the rendered markup, but can be very helpful with complex layouts to determine which component was responsible for which portion of the rendered page.
Adaptable service contributions
When making contributions to a service, you are no longer restricted to contributing a value that is assignable to the type associated with the configuration; objects of any type may be contributed, and the TypeCoercer service is used to coerce the value to the configuration's type.
Component debugging improvements
Because of how Tapestry instruments your pages and components, it has been difficult to debug Tapestry applications; any mutable field shows its
[CONF] Apache Tapestry > Release Notes 5.3
Release Notes 5.3
Page edited by Howard M. Lewis Ship
Comment:
implicit ordered configuration constraints
Changes (1)
...
Form components now recognize when the client-side form was cancelled. A new "cancelled" event is triggered early in the submission process, which allows the page to bypass all property updates and input validations, when desired.
h3. Implicit OrderedConfiguration Constraints When using {{OrderedConfiguration.add()}} with no constraints, Tapestry will now implicitly order the added element after the previously added element, within the same method. In prior releases, such elements were added with no constraints. This makes it easier to contribute a group of related items with an implicit ordering.
h2. Removed Functionality
...
Full Content
Release Notes 5.2 Release Notes
This is the consolidated list of changes between Tapestry versions 5.2 and 5.3. To upgrade from 5.1 to 5.2, most users will be able to just update the Maven dependency in their POM file (or download the new JAR file) and the new version will just work. However, please read carefully below before upgrading.
Contents
Breaking Changes
New Features
Removed Functionality
Release Notes: Tapestry 5.3.0
Sub-task
Bug
Improvement
New Feature
Task
Test
Breaking Changes
Some number of interfaces and APIs in Tapestry 5.3 will be removed in Tapestry 5.4 or later. These include:
The "suppress redirects" functionality, which allows component event requests to respond directly with HTML, as in Tapestry 4
The RenderSupport environmental (replaced with the _javascript_Support environmental)
ClassFactory service and ClassFab interface (replaced with the PlasticProxyFactory service and PlasticClass interface)
Many classes and interfaces marked as deprecated in prior releases of Tapestry have been removed.
Because of the upgrade to Prototype 1.7, existing _javascript_ that uses value.toJSON() may break; replace with Object.toJSON(value).
New Features
Rendering comments
It is now possible to have Tapestry emit rendering comments; these are comments (such as ) that can assist you in debugging markup output on the client-side. This is enabled for all requests using the configuration symbol tapestry.component-render-tracing-enabled, and can be added to any request by adding the query parameter t:component-trace=true to the URL. This will significantly increase the size of the rendered markup, but can be very helpful with complex layouts to determine which component was responsible for which portion of the rendered page.
Adaptable service contributions
When making contributions to a service, you are no longer restricted to contributing a value that is assignable to the type associated with the configuration; objects of any type may be contributed, and the TypeCoercer service is used to coerce the value to the configuration's type.
Component debugging improvements
Because of how Tapestry instruments your pages and components, it has been difficult to debug Tapestry applications; any mutable field shows its default value in the debugger, regardless of what has been written to the field or read out of it. In Tapestry 5.3, when in development mode, Tapestry now shadows values read from or written to such fields into the fields themselves (this has also been fixed in the 5.2.5 maintenance release). This does not occur in production, to avoid potential memory leaks.
Reloading disabled in production
Tapestry no longer checks for changes to Tapestry component class files, templates, or message catalogs in production mode. It is assumed that Tapestry applications are packaged as WAR files in production, and that changing the WAR file causes the servlet container to redeploy the entire application. This change is to improve throughput and reduce memory consumption in production applications.
String-to-Enum coercions
The TypeCoercer service now automatically generates String-to-Enum coercions without requiring a specific contribution. This coercion is case insensitive. A contribution is still allowed, and will take priority over the default coercion, but is only necessary to support "aliases" for enum values outside those defined by the enum type itself.
_javascript_ and CSS minimization
A new optional library, tapestry-yuicompressor, has been added. This library adds support for compressing _javascript_ libraries and CSS files using the YUICompressor library
ComponentClassTransformWorker Service
The type of this service has changed from ComponentClassTransformWorker to ComponentClassTransformWorker2. Contributions of type ComponentClassTransformWorker will automatically be coerce
[CONF] Apache Tapestry > Release Notes 5.3
Release Notes 5.3
Page edited by Howard M. Lewis Ship
Changes (1)
...
h2. Removed Functionality The integrated Blackbird client-side console has been removed. In its place are the floating console messages (used when Blackbird is disabled) combined with logging to the FireBug or WebKit console. This should make debugging client-side _javascript_ much easier.
h2. Release Notes: Tapestry 5.3.0 {include:Release Notes 5.3.0}
...
Full Content
Release Notes 5.2 Release Notes
This is the consolidated list of changes between Tapestry versions 5.2 and 5.3. To upgrade from 5.1 to 5.2, most users will be able to just update the Maven dependency in their POM file (or download the new JAR file) and the new version will just work. However, please read carefully below before upgrading.
Contents
Breaking Changes
New Features
Removed Functionality
Release Notes: Tapestry 5.3.0
Sub-task
Bug
Improvement
New Feature
Task
Test
Breaking Changes
Some number of interfaces and APIs in Tapestry 5.3 will be removed in Tapestry 5.4 or later. These include:
The "suppress redirects" functionality, which allows component event requests to respond directly with HTML, as in Tapestry 4
The RenderSupport environmental (replaced with the _javascript_Support environmental)
ClassFactory service and ClassFab interface (replaced with the PlasticProxyFactory service and PlasticClass interface)
Many classes and interfaces marked as deprecated in prior releases of Tapestry have been removed.
New Features
Rendering comments
It is now possible to have Tapestry emit rendering comments; these are comments (such as ) that can assist you in debugging markup output on the client-side. This is enabled for all requests using the configuration symbol tapestry.component-render-tracing-enabled, and can be added to any request by adding the query parameter t:component-trace=true to the URL. This will significantly increase the size of the rendered markup, but can be very helpful with complex layouts to determine which component was responsible for which portion of the rendered page.
Adaptable service contributions
When making contributions to a service, you are no longer restricted to contributing a value that is assignable to the type associated with the configuration; objects of any type may be contributed, and the TypeCoercer service is used to coerce the value to the configuration's type.
Component debugging improvements
Because of how Tapestry instruments your pages and components, it has been difficult to debug Tapestry applications; any mutable field shows its default value in the debugger, regardless of what has been written to the field or read out of it. In Tapestry 5.3, when in development mode, Tapestry now shadows values read from or written to such fields into the fields themselves (this has also been fixed in the 5.2.5 maintenance release). This does not occur in production, to avoid potential memory leaks.
Reloading disabled in production
Tapestry no longer checks for changes to Tapestry component class files, templates, or message catalogs in production mode. It is assumed that Tapestry applications are packaged as WAR files in production, and that changing the WAR file causes the servlet container to redeploy the entire application. This change is to improve throughput and reduce memory consumption in production applications.
String-to-Enum coercions
The TypeCoercer service now automatically generates String-to-Enum coercions without requiring a specific contribution. This coercion is case insensitive. A contribution is still allowed, and will take priority over the default coercion, but is only necessary to support "aliases" for enum values outside those defined by the enum type itself.
_javascript_ and CSS minimization
A new optional library, tapestry-yuicompressor, has been added. This library adds support for compressing _javascript_ libraries and CSS files using the YUICompressor library
ComponentClassTransformWorker Service
The type of this service has changed from ComponentClassTransformWorker to ComponentClassTransformWorker2. Contributions of type ComponentClassTransformWorker will automatically be coerced to the new ComponentClassTransformWorker2 interface. However, if you use the @Contribute annotation to mark the method that makes contributions, you will need to update the annotation to indicate the new service interface. If you followed the naming convention, and named your method contributeComponentClassTransformWorker(), you don't need to change anything.
Tapestry JavaDoc
Tapestry now includes a new library, tapestry-javadoc, that replaces the old Maven-based component report. Si
[CONF] Apache Tapestry > Release Notes 5.2.6
Release Notes 5.2.6
Page edited by Howard M. Lewis Ship
Changes (1)
Tapestry 5.2.6 is a bug fix maintenance release.
{html}
...
Full Content
Tapestry 5.2.6 is a maintenance release.
Bug
[TAP5-1368] - The onFailure function provided to Tapestry.ajaxRequest does not always get invoked
[TAP5-1546] - TranslatorSource incorrectly annotated with @UsesConfiguration when it should now be @UsesMappedConfiguration (as of 5.2)
[TAP5-1551] - FormFragment change visibility/hide and remove event listeners should call event.stop() to prevent container fragments from also being hidden
Improvement
[TAP5-1482] - Upgrade Prototype to 1.7 / Scriptaculous 1.9.0
[TAP5-1538] - Optimize client-side URL rebuilding in IE 7
[TAP5-1539] - Optimize document scans used by Tapestry.FieldEventManager to not locate the label or icon until actually needed
Change Notification Preferences
View Online
|
View Changes
[CONF] Apache Tapestry > Release Notes 5.2.6
Release Notes 5.2.6
Page edited by Howard M. Lewis Ship
Changes (4)
...
{html}
23>Bug
23>
[
...
23>Improvement
23>
[
...
Full Content
Tapestry 5.2.6 is a bug fix release.
Bug
[TAP5-1368] - The onFailure function provided to Tapestry.ajaxRequest does not always get invoked
[TAP5-1546] - TranslatorSource incorrectly annotated with @UsesConfiguration when it should now be @UsesMappedConfiguration (as of 5.2)
[TAP5-1551] - FormFragment change visibility/hide and remove event listeners should call event.stop() to prevent container fragments from also being hidden
Improvement
[TAP5-1482] - Upgrade Prototype to 1.7 / Scriptaculous 1.9.0
[TAP5-1538] - Optimize client-side URL rebuilding in IE 7
[TAP5-1539] - Optimize document scans used by Tapestry.FieldEventManager to not locate the label or icon until actually needed
Change Notification Preferences
View Online
|
View Changes
[CONF] Apache Tapestry > Release Notes 5.2.6
Release Notes 5.2.6
Page edited by Howard M. Lewis Ship
Changes (2)
Tapestry 5.2.6 is a bug fix release.
{html} Bug [ [ [ Improvement [ [ [ {html}
Full Content
Tapestry 5.2.6 is a bug fix release.
Bug
[TAP5-1368] - The onFailure function provided to Tapestry.ajaxRequest does not always get invoked
[TAP5-1546] - TranslatorSource incorrectly annotated with @UsesConfiguration when it should now be @UsesMappedConfiguration (as of 5.2)
[TAP5-1551] - FormFragment change visibility/hide and remove event listeners should call event.stop() to prevent container fragments from also being hidden
Improvement
[TAP5-1482] - Upgrade Prototype to 1.7 / Scriptaculous 1.9.0
[TAP5-1538] - Optimize client-side URL rebuilding in IE 7
[TAP5-1539] - Optimize document scans used by Tapestry.FieldEventManager to not locate the label or icon until actually needed
Change Notification Preferences
View Online
|
View Changes
[CONF] Apache Tapestry > Release Notes 5.2.6
Release Notes 5.2.6 Page added by Howard M. Lewis Ship Change Notification Preferences View Online
[CONF] Apache Tapestry > Release Notes 5.2.6
Release Notes 5.2.6 Page added by Howard M. Lewis Ship Change Notification Preferences View Online
[CONF] Apache Tapestry > Release Notes 5.3.0
Release Notes 5.3.0
Page edited by Howard M. Lewis Ship
Changes (7)
{scrollbar}
h5. Rendering comments
{html}
It is now possible to have Tapestry emit rendering comments; these are comments (such as {{}}) that can assist you in debugging markup output on the client-side. This is enabled for all requests using the configuration symbol {{tapestry.component-render-tracing-enabled}}, and can be added to any request by adding the query parameter {{t:component-trace=true}} to the URL. This will significantly increase the size of the rendered markup, but can be very helpful with complex layouts to determine which component was responsible for which portion of the rendered page.
Release Note Release Notes - Tapestry 5 - Version 5.3.0 Sub-task [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ Bug [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ Improvement [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ New Feature [ [ [ [ [ [ [ [ [ [ Task [ [ [ [ [ [ Test [ {html}
h5. Adaptable service contributions
When making contributions to a service, you are no longer restricted to contributing a value that is assignable to the type associated with the configuration; objects of any type may be contributed, and the TypeCoercer service is used to coerce the value to the configuration's type.
h5. Component debugging improvements Because of how Tapestry instruments your pages and components, it has been difficult to debug Tapestry applications; any mutable field shows its default value in the debugger, regardless of what has been written to the field or read out of it. In Tapestry 5.3, when in _development mode_, Tapestry now shadows values read from or written to such fields into the fields themselves (this has also been fixed in the 5.2.5 maintenance release). This does not occur in production, to avoid potential memory leaks. h5. Reloading disabled in production Tapestry no longer checks for changes to Tapestry component class files, templates, or message catalogs in production mode. It is assumed that Tapestry applications are packaged as WAR files in production, and that changing the WAR file causes the servlet container to redeploy the entire application. This change is to improve throughput and reduce memory consumption in production applications. h5. String-to-Enum coercions The TypeCoercer service now automatically generates String-to-Enum coercions without requiring a specific contribution. This coercion is case insensitive. A contribution is still allowed, and will take priority over the default coercion, but is only necessary to support "aliases" for enum values outside those defined by the enum type itself. h5. _javascript_ and CSS minimization A new optional library, tapestry-yuicompressor, has been added. This library adds support for compressing _javascript_ libraries and CSS files using [the YUICompressor library|http://developer.yahoo.com/yui/compressor/] h5. ComponentClassTransformWorker Service The type of this service has changed from ComponentClassTransformWorker to ComponentClassTransformWorker2. Contributions of type ComponentClassTransformWorker will automatically be coerced to the new ComponentClassTransformWorker2 interface. However, if you use the @Contribute annotation to mark the method that makes contributions, you will need to update the annotation to indicate the new service interface. If you followed the naming convention, and named your method {{contributeComponentClassTransformWorker()}}, you don't need to change anything. h5. Tapestry JavaDoc Tapestry now includes a new library, tapestry-javadoc, that replaces the old Maven-based component report. Simply by placing a @tapestrydoc annotation into your component's JavaDoc, Tapestry will generate complete documentation as part of JavaDoc ... no more switching back and forth, and no more reliance on Maven for component documentation. h5. Skinning / Theming Support Tapestry now adds the ability to skin and/or theme your pages and components. Its an extension of how Tapestry manages pages per locale, but adds new application-defined _axes_ along with rules to find the resources. There's also a new Dynamic component, which uses an external template, not a Tapestry template, which can be chosen at runtime. h5. Tree Component Tapestry finally has a proper Tree component for navigating hierarchical data. It's efficient and Ajax-enabled, and fully customizable. h5. Deprecations Some number of interfaces and APIs in Tapestry 5.3 will be removed in Tapestry 5.4 or later. These include: * The "suppress redirects" functionality, which allows component event requests t
[CONF] Apache Tapestry > Release Notes 5.3
Release Notes 5.3
Page edited by Howard M. Lewis Ship
Changes (2)
...
h2. Breaking Changes
Some number of interfaces and APIs in Tapestry 5.3 will be removed in Tapestry 5.4 or later. These include: * The "suppress redirects" functionality, which allows component event requests to respond directly with HTML, as in Tapestry 4 * The RenderSupport environmental (replaced with the _javascript_Support environmental) * ClassFactory service and ClassFab interface (replaced with the PlasticProxyFactory service and PlasticClass interface)
Many classes and interfaces marked as deprecated in prior releases of Tapestry have been removed.
h2. New Features h3. Rendering comments It is now possible to have Tapestry emit rendering comments; these are comments (such as {{}}) that can assist you in debugging markup output on the client-side. This is enabled for all requests using the configuration symbol {{tapestry.component-render-tracing-enabled}}, and can be added to any request by adding the query parameter {{t:component-trace=true}} to the URL. This will significantly increase the size of the rendered markup, but can be very helpful with complex layouts to determine which component was responsible for which portion of the rendered page. h3. Adaptable service contributions When making contributions to a service, you are no longer restricted to contributing a value that is assignable to the type associated with the configuration; objects of any type may be contributed, and the TypeCoercer service is used to coerce the value to the configuration's type. h3. Component debugging improvements Because of how Tapestry instruments your pages and components, it has been difficult to debug Tapestry applications; any mutable field shows its default value in the debugger, regardless of what has been written to the field or read out of it. In Tapestry 5.3, when in _development mode_, Tapestry now shadows values read from or written to such fields into the fields themselves (this has also been fixed in the 5.2.5 maintenance release). This does not occur in production, to avoid potential memory leaks. h3. Reloading disabled in production Tapestry no longer checks for changes to Tapestry component class files, templates, or message catalogs in production mode. It is assumed that Tapestry applications are packaged as WAR files in production, and that changing the WAR file causes the servlet container to redeploy the entire application. This change is to improve throughput and reduce memory consumption in production applications. h3. String-to-Enum coercions The TypeCoercer service now automatically generates String-to-Enum coercions without requiring a specific contribution. This coercion is case insensitive. A contribution is still allowed, and will take priority over the default coercion, but is only necessary to support "aliases" for enum values outside those defined by the enum type itself. h3. _javascript_ and CSS minimization A new optional library, tapestry-yuicompressor, has been added. This library adds support for compressing _javascript_ libraries and CSS files using [the YUICompressor library|http://developer.yahoo.com/yui/compressor/] h3. ComponentClassTransformWorker Service The type of this service has changed from ComponentClassTransformWorker to ComponentClassTransformWorker2. Contributions of type ComponentClassTransformWorker will automatically be coerced to the new ComponentClassTransformWorker2 interface. However, if you use the @Contribute annotation to mark the method that makes contributions, you will need to update the annotation to indicate the new service interface. If you followed the naming convention, and named your method {{contributeComponentClassTransformWorker()}}, you don't need to change anything. h3. Tapestry JavaDoc Tapestry now includes a new library, tapestry-javadoc, that replaces the old Maven-based component report. Simply by placing a @tapestrydoc annotation into your component's JavaDoc, Tapestry will generate complete documentation as part of JavaDoc ... no more switching back and forth, and no more reliance on Maven for component documentation. h3. Skinning / Theming Support Tapestry now adds the ability to skin and/or theme your pages and components. Its an extension of how Tapestry manages pages per locale, but adds new application-defined _axes_ along with rules to find the resources. There's also a new Dynamic component, which uses an external template, not a Tapestry template, which can be chosen at runtime. h3. Tree Component Tapestry finally has a proper Tree component for navigating hierarchical data. It's efficient and Ajax-enabled, and fully customizable.
h2. Release Notes: Tapestry 5.3.0 {include:Release Notes 5.3.0}
...
[CONF] Apache Tapestry > Release Notes 5.2.5
Release Notes 5.2.5 Page moved by Howard M. Lewis Ship From: Apache Tapestry > Release Notes To: Apache Tapestry > Release Notes 5.2 Children moved Change Notification Preferences View Online
[CONF] Apache Tapestry > Release Notes 5.3.0
Release Notes 5.3.0 Page moved by Howard M. Lewis Ship From: Apache Tapestry > Release Notes To: Apache Tapestry > Release Notes 5.3 Children moved Change Notification Preferences View Online
[CONF] Apache Tapestry > Release Notes 5.3
Release Notes 5.3 Page added by Howard M. Lewis Ship Release Notes This is the consolidated list of changes between Tapestry versions 5.2 and 5.3. To upgrade from 5.1 to 5.2, most users will be able to just update the Maven dependency in their POM file (or download the new JAR file) and the new version will just work. However, please read carefully below before upgrading. Contents Breaking Changes Release Notes: Tapestry 5.3.0 Breaking Changes Many classes and interfaces marked as deprecated in prior releases of Tapestry have been removed. Release Notes: Tapestry 5.3.0 Release Notes 5.2.5 Release Notes Rendering comments It is now possible to have Tapestry emit rendering comments; these are comments (such as ) that can assist you in debugging markup output on the client-side. This is enabled for all requests using the configuration symbol tapestry.component-render-tracing-enabled, and can be added to any request by adding the query parameter t:component-trace=true to the URL. This will significantly increase the size of the rendered markup, but can be very helpful with complex layouts to determine which component was responsible for which portion of the rendered page. Adaptable service contributions When making contributions to a service, you are no longer restricted to contributing a value that is assignable to the type associated with the configuration; objects of any type may be contributed, and the TypeCoercer service is used to coerce the value to the configuration's type. Component debugging improvements Because of how Tapestry instruments your pages and components, it has been difficult to debug Tapestry applications; any mutable field shows its default value in the debugger, regardless of what has been written to the field or read out of it. In Tapestry 5.3, when in development mode, Tapestry now shadows values read from or written to such fields into the fields themselves (this has also been fixed in the 5.2.5 maintenance release). This does not occur in production, to avoid potential memory leaks. Reloading disabled in production Tapestry no longer checks for changes to Tapestry component class files, templates, or message catalogs in production mode. It is assumed that Tapestry applications are packaged as WAR files in production, and that changing the WAR file causes the servlet container to redeploy the entire application. This change is to improve throughput and reduce memory consumption in production applications. String-to-Enum coercions The TypeCoercer service now automatically generates String-to-Enum coercions without requiring a specific contribution. This coercion is case insensitive. A contribution is still allowed, and will take priority over the default coercion, but is only necessary to support "aliases" for enum values outside those defined by the enum type itself. _javascript_ and CSS minimization A new optional library, tapestry-yuicompressor, has been added. This library adds support for compressing _javascript_ libraries and CSS files using the YUICompressor library ComponentClassTransformWorker Service The type of this service has changed from ComponentClassTransformWorker to ComponentClassTransformWorker2. Contributions of type ComponentClassTransformWorker will automatically be coerced to the new ComponentClassTransformWorker2 interface. However, if you use the @Contribute annotation to mark the method that makes contributions, you will need to update the annotation to indicate the new service interface. If you followed the naming convention, and named your method contributeComponentClassTransformWorker(), you don't need to change anything. Tapestry JavaDoc Tapestry now includes a new library, tapestry-javadoc, that replaces the old Maven-based component report. Simply by placing a @tapestrydoc annotation into your component's JavaDoc, Tapestry will generate complete documentation as part of JavaDoc ... no more switching back and forth, and no more reliance on Maven for component documentation. Skinning / Theming Support Tapestry now adds the ability to skin and/or theme your pages and components. Its an extension of how Tapestry manages pages per locale, but adds new application-defined axes along with rules to find the resources. There's also a new Dynamic component, which uses an external template, not a Tapestry template, which can be chosen at runtime. Tree Component Tapestry finally has a proper Tree component for navigating hierarchical data. It's efficient and Ajax-enabled, and fully customizable. Deprecations Some number of interfaces and APIs in Tapestry 5.3 will be removed in Tapestry 5.4 or later. These include: The "suppress redirects" functionality, which allows component event requests to respond directly with HTML, as in Tapestry 4 The RenderSupport environmental (replaced with the _javascript_Support environmental) ClassFactory service and ClassFab i
[CONF] Apache Tapestry > Release Notes
Release Notes Page edited by Howard M. Lewis Ship Changes (3) These release notes provide the details of the changes in each Tapestry version. || Tapestry 5.3 | [Tapestry 5.3.0|Release Notes 5.3.0] | _Current alpha release_ | || Tapestry 5.3 | [Consolidated Release Notes for 5.3|Release Notes 5.3] | _Current alpha release_ | || | [Release Notes 5.3.0] | Released 22 Jun 2011 | || Tapestry 5.2 | [Consolidated Release Notes for 5.2|Release Notes 5.2] | *This is the current stable release* | || | [Release Notes 5.2.5] | Released 23 Mar 2011 | ... || | [Release Notes 5.2.1] | Released 29 Sep 2010 | || | [Release Notes 5.2.0] | Released 8 Aug 2010 | || Tapestry 5.1| [Release Notes 5.1] | Released Apr 23, 12Apr 2009 | || Tapestry 5.0| [Release Notes 5.0] | Released Dec 2008 | Full Content These release notes provide the details of the changes in each Tapestry version. Tapestry 5.3 Consolidated Release Notes for 5.3 Current alpha release Release Notes 5.3.0 Released 22 Jun 2011 Tapestry 5.2 Consolidated Release Notes for 5.2 This is the current stable release Release Notes 5.2.5 Released 23 Mar 2011 Release Notes 5.2.4 Released 15 Nov 2010 Release Notes 5.2.3 Released 11 Nov 2010 Release Notes 5.2.2 Released 24 Oct 2010 Release Notes 5.2.1 Released 29 Sep 2010 Release Notes 5.2.0 Released 8 Aug 2010 Tapestry 5.1 Release Notes 5.1 Released 12Apr 2009 Tapestry 5.0 Release Notes 5.0 Released Dec 2008 Change Notification Preferences View Online | View Changes
[CONF] Apache Tapestry > Release Notes
Release Notes Page edited by Howard M. Lewis Ship Changes (1) These release notes provide the details of the changes in each Tapestry version. || Tapestry 5.3 | [Tapestry 5.3.0|Release Notes 5.3.0] | _Not yet released_ _Current alpha release_ | || Tapestry 5.2 | [Consolidated Release Notes for 5.2|Release Notes 5.2] | *This is the current stable release* | || | [Release Notes 5.2.5] | Released 23 Mar 2011 | ... Full Content These release notes provide the details of the changes in each Tapestry version. Tapestry 5.3 Tapestry 5.3.0 Current alpha release Tapestry 5.2 Consolidated Release Notes for 5.2 This is the current stable release Release Notes 5.2.5 Released 23 Mar 2011 Release Notes 5.2.4 Released 15 Nov 2010 Release Notes 5.2.3 Released 11 Nov 2010 Release Notes 5.2.2 Released 24 Oct 2010 Release Notes 5.2.1 Released 29 Sep 2010 Release Notes 5.2.0 Released 8 Aug 2010 Tapestry 5.1 Release Notes 5.1 Released Apr 23, 2009 Tapestry 5.0 Release Notes 5.0 Released Dec 2008 Change Notification Preferences View Online | View Changes
[CONF] Apache Tapestry > Release Notes 5.3.0
Release Notes 5.3.0
Page edited by Howard M. Lewis Ship
Changes (1)
...
The type of this service has changed from ComponentClassTransformWorker to ComponentClassTransformWorker2. Contributions of type ComponentClassTransformWorker will automatically be coerced to the new ComponentClassTransformWorker2 interface. However, if you use the @Contribute annotation to mark the method that makes contributions, you will need to update the annotation to indicate the new service interface. If you followed the naming convention, and named your method {{contributeComponentClassTransformWorker()}}, you don't need to change anything.
h5. Tapestry JavaDoc Tapestry now includes a new library, tapestry-javadoc, that replaces the old Maven-based component report. Simply by placing a @tapestrydoc annotation into your component's JavaDoc, Tapestry will generate complete documentation as part of JavaDoc ... no more switching back and forth, and no more reliance on Maven for component documentation. h5. Skinning / Theming Support Tapestry now adds the ability to skin and/or theme your pages and components. Its an extension of how Tapestry manages pages per locale, but adds new application-defined _axes_ along with rules to find the resources. There's also a new Dynamic component, which uses an external template, not a Tapestry template, which can be chosen at runtime. h5. Tree Component Tapestry finally has a proper Tree component for navigating hierarchical data. It's efficient and Ajax-enabled, and fully customizable.
h5. Deprecations
...
Full Content
Release Notes 5.2.5 Release Notes
Rendering comments
It is now possible to have Tapestry emit rendering comments; these are comments (such as ) that can assist you in debugging markup output on the client-side. This is enabled for all requests using the configuration symbol tapestry.component-render-tracing-enabled, and can be added to any request by adding the query parameter t:component-trace=true to the URL. This will significantly increase the size of the rendered markup, but can be very helpful with complex layouts to determine which component was responsible for which portion of the rendered page.
Adaptable service contributions
When making contributions to a service, you are no longer restricted to contributing a value that is assignable to the type associated with the configuration; objects of any type may be contributed, and the TypeCoercer service is used to coerce the value to the configuration's type.
Component debugging improvements
Because of how Tapestry instruments your pages and components, it has been difficult to debug Tapestry applications; any mutable field shows its default value in the debugger, regardless of what has been written to the field or read out of it. In Tapestry 5.3, when in development mode, Tapestry now shadows values read from or written to such fields into the fields themselves (this has also been fixed in the 5.2.5 maintenance release). This does not occur in production, to avoid potential memory leaks.
Reloading disabled in production
Tapestry no longer checks for changes to Tapestry component class files, templates, or message catalogs in production mode. It is assumed that Tapestry applications are packaged as WAR files in production, and that changing the WAR file causes the servlet container to redeploy the entire application. This change is to improve throughput and reduce memory consumption in production applications.
String-to-Enum coercions
The TypeCoercer service now automatically generates String-to-Enum coercions without requiring a specific contribution. This coercion is case insensitive. A contribution is still allowed, and will take priority over the default coercion, but is only necessary to support "aliases" for enum values outside those defined by the enum type itself.
_javascript_ and CSS minimization
A new optional library, tapestry-yuicompressor, has been added. This library adds support for compressing _javascript_ libraries and CSS files using the YUICompressor library
ComponentClassTransformWorker Service
The type of this service has changed from ComponentClassTransformWorker to ComponentClassTransformWorker2. Contributions of type ComponentClassTransformWorker will automatically be coerced to the new ComponentClassTransformWorker2 interface. However, if you use the @Contribute annotation to mark the method that makes contributions, you will need to update the annotation to indicate the new service interface. If you followed the naming convention, and named your method contributeComponentClassTransformWorker(), you don't need to change anything.
Tapestry JavaDoc
Tapestry now includes a new library, tapestry-javadoc,
[CONF] Apache Tapestry > Release Notes 5.3.0
Release Notes 5.3.0
Page edited by Howard M. Lewis Ship
Changes (1)
...
A new optional library, tapestry-yuicompressor, has been added. This library adds support for compressing _javascript_ libraries and CSS files using [the YUICompressor library|http://developer.yahoo.com/yui/compressor/]
h5. ComponentClassTransformWorker Service The type of this service has changed from ComponentClassTransformWorker to ComponentClassTransformWorker2. Contributions of type ComponentClassTransformWorker will automatically be coerced to the new ComponentClassTransformWorker2 interface. However, if you use the @Contribute annotation to mark the method that makes contributions, you will need to update the annotation to indicate the new service interface. If you followed the naming convention, and named your method {{contributeComponentClassTransformWorker()}}, you don't need to change anything.
h5. Deprecations
...
Full Content
Release Notes 5.2.5 Release Notes
Rendering comments
It is now possible to have Tapestry emit rendering comments; these are comments (such as ) that can assist you in debugging markup output on the client-side. This is enabled for all requests using the configuration symbol tapestry.component-render-tracing-enabled, and can be added to any request by adding the query parameter t:component-trace=true to the URL. This will significantly increase the size of the rendered markup, but can be very helpful with complex layouts to determine which component was responsible for which portion of the rendered page.
Adaptable service contributions
When making contributions to a service, you are no longer restricted to contributing a value that is assignable to the type associated with the configuration; objects of any type may be contributed, and the TypeCoercer service is used to coerce the value to the configuration's type.
Component debugging improvements
Because of how Tapestry instruments your pages and components, it has been difficult to debug Tapestry applications; any mutable field shows its default value in the debugger, regardless of what has been written to the field or read out of it. In Tapestry 5.3, when in development mode, Tapestry now shadows values read from or written to such fields into the fields themselves (this has also been fixed in the 5.2.5 maintenance release). This does not occur in production, to avoid potential memory leaks.
Reloading disabled in production
Tapestry no longer checks for changes to Tapestry component class files, templates, or message catalogs in production mode. It is assumed that Tapestry applications are packaged as WAR files in production, and that changing the WAR file causes the servlet container to redeploy the entire application. This change is to improve throughput and reduce memory consumption in production applications.
String-to-Enum coercions
The TypeCoercer service now automatically generates String-to-Enum coercions without requiring a specific contribution. This coercion is case insensitive. A contribution is still allowed, and will take priority over the default coercion, but is only necessary to support "aliases" for enum values outside those defined by the enum type itself.
_javascript_ and CSS minimization
A new optional library, tapestry-yuicompressor, has been added. This library adds support for compressing _javascript_ libraries and CSS files using the YUICompressor library
ComponentClassTransformWorker Service
The type of this service has changed from ComponentClassTransformWorker to ComponentClassTransformWorker2. Contributions of type ComponentClassTransformWorker will automatically be coerced to the new ComponentClassTransformWorker2 interface. However, if you use the @Contribute annotation to mark the method that makes contributions, you will need to update the annotation to indicate the new service interface. If you followed the naming convention, and named your method contributeComponentClassTransformWorker(), you don't need to change anything.
Deprecations
Some number of interfaces and APIs in Tapestry 5.3 will be removed in Tapestry 5.4 or later. These include:
The "suppress redirects" functionality, which allows component event requests to respond directly with HTML, as in Tapestry 4
The RenderSupport environmental (replaced with the _javascript_Support environmental)
ClassFactory service and ClassFab interface (replaced with the PlasticProxyFactory service and PlasticClass interface)
Release Notes 5.2.5 Release Notes
Change Notification Preferences
View Online
|
View Changes
[CONF] Apache Tapestry > Release Notes 5.3.0
Release Notes 5.3.0 Page edited by Howard M. Lewis Ship Changes (1) ... Some number of interfaces and APIs in Tapestry 5.3 will be removed in Tapestry 5.4 or later. These include: * The "suppress redirects" functionality, which allows component event requests to response respond directly with HTML, as in Tapestry 4 * The RenderSupport environmental (replaced with the _javascript_Support environmental) * ClassFactory service and ClassFab interface (replaced with the PlasticProxyFactory service and PlasticClass interface) ... Full Content Release Notes 5.2.5 Release Notes Rendering commments It is now possible to have Tapestry emit rendering comments; these are comments (such as ) that can assist you in debugging markup output on the client-side. This is enabled for all requests using the configuration symbol tapestry.component-render-tracing-enabled, and can be added to any request by adding the query parameter t:component-trace=true to the URL. This will significantly increase the size of the rendered markup, but can be very helpful with complex layouts to determine which component was responsible for which portion of the rendered page. Adaptable service contributions When making contributions to a service, you are no longer restricted to contributing a value that is assignable to the type associated with the configuration; objects of any type may be contributed, and the TypeCoercer service is used to coerce the value to the configuration's type. Component debugging improvements Because of how Tapestry instruments your pages and components, it has been difficult to debug Tapestry applications; any mutable field shows its default value in the debugger, regardless of what has been written to the field or read out of it. In Tapestry 5.3, when in development mode, Tapestry now shadows values read from or written to such fields into the fields themselves (this has also been fixed in the 5.2.5 maintenance release). This does not occur in production, to avoid potential memory leaks. Reloading disabled in production Tapestry no longer checks for changes to Tapestry component class files, templates, or message catalogs in production mode. It is assumed that Tapestry applications are packaged as WAR files in production, and that changing the WAR file causes the servlet container to redeploy the entire application. This change is to improve throughput and reduce memory consumption in production applications. String-to-Enum coercions The TypeCoercer service now automatically generates String-to-Enum coercions without requiring a specific contribution. This coercion is case insensitive. A contribution is still allowed, and will take priority over the default coercion, but is only necessary to support "aliases" for enum values outside those defined by the enum type itself. _javascript_ and CSS minimization A new optional library, tapestry-yuicompressor, has been added. This library adds support for compressing _javascript_ libraries and CSS files using the YUICompressor library Deprecations Some number of interfaces and APIs in Tapestry 5.3 will be removed in Tapestry 5.4 or later. These include: The "suppress redirects" functionality, which allows component event requests to respond directly with HTML, as in Tapestry 4 The RenderSupport environmental (replaced with the _javascript_Support environmental) ClassFactory service and ClassFab interface (replaced with the PlasticProxyFactory service and PlasticClass interface) Release Notes 5.2.5 Release Notes Change Notification Preferences View Online | View Changes
[CONF] Apache Tapestry > Release Notes 5.3.0
Release Notes 5.3.0
Page edited by Howard M. Lewis Ship
Comment:
Keep release notes up to date with recent changes
Changes (4)
{scrollbar}
h5. Rendering commments
It is now possible to have Tapestry emit rendering comments; these are comments (such as {{}}) that can assist you in debugging markup output on the client-side. This is enabled for all requests using the configuration symbol {{tapestry.component-render-tracing-enabled}}, and can be added to any request by adding the query parameter {{t:component-trace=true}} to the URL. This will significantly increase the size of the rendered markup, but can be very helpful with complex layouts to determine which component was responsible for which portion of the rendered page.
h5. Adaptable service contributions
When making contributions to a service, you are no longer restricted to contributing a value that is assignable to the type associated with the configuration; objects of any type may be contributed, and the TypeCoercer service is used to coerce the value to the configuration's type.
h5. Component debugging improvements
Because of how Tapestry instruments your pages and components, it has been difficult to debug Tapestry applications; any mutable field shows its default value in the debugger, regardless of what has been written to the field or read out of it. In Tapestry 5.3, when in _development mode_, Tapestry now shadows values read from or written to such fields into the fields themselves (this has also been fixed in the 5.2.5 maintenance release). This does not occur in production, to avoid potential memory leaks.
h5. Reloading disabled in production Tapestry no longer checks for changes to Tapestry component class files, templates, or message catalogs in production mode. It is assumed that Tapestry applications are packaged as WAR files in production, and that changing the WAR file causes the servlet container to redeploy the entire application. This change is to improve throughput and reduce memory consumption in production applications. h5. String-to-Enum coercions The TypeCoercer service now automatically generates String-to-Enum coercions without requiring a specific contribution. This coercion is case insensitive. A contribution is still allowed, and will take priority over the default coercion, but is only necessary to support "aliases" for enum values outside those defined by the enum type itself. h5. _javascript_ and CSS minimization A new optional library, tapestry-yuicompressor, has been added. This library adds support for compressing _javascript_ libraries and CSS files using [the YUICompressor library|http://developer.yahoo.com/yui/compressor/] h5. Deprecations Some number of interfaces and APIs in Tapestry 5.3 will be removed in Tapestry 5.4 or later. These include: * The "suppress redirects" functionality, which allows component event requests to response directly with HTML, as in Tapestry 4 * The RenderSupport environmental (replaced with the _javascript_Support environmental) * ClassFactory service and ClassFab interface (replaced with the PlasticProxyFactory service and PlasticClass interface)
{scrollbar}
Full Content
Release Notes 5.2.5 Release Notes
Rendering commments
It is now possible to have Tapestry emit rendering comments; these are comments (such as ) that can assist you in debugging markup output on the client-side. This is enabled for all requests using the configuration symbol tapestry.component-render-tracing-enabled, and can be added to any request by adding the query parameter t:component-trace=true to the URL. This will significantly increase the size of the rendered markup, but can be very helpful with complex layouts to determine which component was responsible for which portion of the rendered page.
Adaptable service contributions
When making contributions to a service, you are no longer restricted to contributing a value that is assignable to the type associated with the configuration; objects of any type may be contributed, and the TypeCoercer service is used to coerce the value to the configuration's type.
Component debugging improvements
Because of how Tapestry instruments your pages and components, it has been difficult to debug Tapestry applications; any mutable field shows its default value in the debugger, regardless of what has been written to the field or read out of it. In Tapestry 5.3, when in development mode, Tapestry now shadows values read from or written to such fields into the fields themselves (this has also been fixed in the 5.2.5 maintenance release). This does not occur in production, to avoid potential memory leak
[CONF] Apache Tapestry > Release Notes 5.2.5
Release Notes 5.2.5 Page edited by Igor Drobiazko Changes (1) ... * [TAP5-1208|https://issues.apache.org/jira/browse/TAP5-1208] - In development mode, Tapestry should "shadow" field & parameter values to instance variables, to assist with debugging * [TAP5-1346|https://issues.apache.org/jira/browse/TAP5-1346] - Fix broken links on new Web Site * [TAP5-1378|https://issues.apache.org/jira/browse/TAP5-1378] - Allow Delegate component to be used for creating in-template components Full Content Version 5.2.5 is a maintenance release for 5.2.4. Bug TAP5-1372 - BaseURLSource uses getLocalPort() rather than getServerPort() Improvement TAP5-1040 - Allow HTML5 doctype to be printed TAP5-1208 - In development mode, Tapestry should "shadow" field & parameter values to instance variables, to assist with debugging TAP5-1346 - Fix broken links on new Web Site Change Notification Preferences View Online | View Changes
[CONF] Apache Tapestry > Release Notes 5.2.5
Release Notes 5.2.5 Page edited by Igor Drobiazko Changes (1) ... * [TAP5-1346|https://issues.apache.org/jira/browse/TAP5-1346] - Fix broken links on new Web Site * [TAP5-1378|https://issues.apache.org/jira/browse/TAP5-1378] - Allow Delegate component to be used for creating in-template components h3. New Feature * [TAP5-742|https://issues.apache.org/jira/browse/TAP5-742] - Add optional component tracing comments to rendered output Full Content Version 5.2.5 is a maintenance release for 5.2.4. Bug TAP5-1372 - BaseURLSource uses getLocalPort() rather than getServerPort() Improvement TAP5-1040 - Allow HTML5 doctype to be printed TAP5-1208 - In development mode, Tapestry should "shadow" field & parameter values to instance variables, to assist with debugging TAP5-1346 - Fix broken links on new Web Site TAP5-1378 - Allow Delegate component to be used for creating in-template components Change Notification Preferences View Online | View Changes
[CONF] Apache Tapestry > Release Notes 5.3.0
Release Notes 5.3.0
Page edited by Howard M. Lewis Ship
Changes (1)
...
It is now possible to have Tapestry emit rendering comments; these are comments (such as {{}}) that can assist you in debugging markup output on the client-side. This is enabled for all requests using the configuration symbol {{tapestry.component-render-tracing-enabled}}, and can be added to any request by adding the query parameter {{t:component-trace=true}} to the URL. This will significantly increase the size of the rendered markup, but can be very helpful with complex layouts to determine which component was responsible for which portion of the rendered page.
When making contributions to a service, you are no longer restricted to contributing a value that is assignable to the type associated with the configuration; objects of any type may be contributed, and the TypeCoercer service is used to coerce the value to the configuration's type. Because of how Tapestry instruments your pages and components, it has been difficult to debug Tapestry applications; any mutable field shows its default value in the debugger, regardless of what has been written to the field or read out of it. In Tapestry 5.3, when in _development mode_, Tapestry now shadows values read from or written to such fields into the fields themselves (this has also been fixed in the 5.2.5 maintenance release). This does not occur in production, to avoid potential memory leaks.
{scrollbar}
Full Content
Release Notes 5.2.5 Release Notes
It is now possible to have Tapestry emit rendering comments; these are comments (such as ) that can assist you in debugging markup output on the client-side. This is enabled for all requests using the configuration symbol tapestry.component-render-tracing-enabled, and can be added to any request by adding the query parameter t:component-trace=true to the URL. This will significantly increase the size of the rendered markup, but can be very helpful with complex layouts to determine which component was responsible for which portion of the rendered page.
When making contributions to a service, you are no longer restricted to contributing a value that is assignable to the type associated with the configuration; objects of any type may be contributed, and the TypeCoercer service is used to coerce the value to the configuration's type.
Because of how Tapestry instruments your pages and components, it has been difficult to debug Tapestry applications; any mutable field shows its default value in the debugger, regardless of what has been written to the field or read out of it. In Tapestry 5.3, when in development mode, Tapestry now shadows values read from or written to such fields into the fields themselves (this has also been fixed in the 5.2.5 maintenance release). This does not occur in production, to avoid potential memory leaks.
Release Notes 5.2.5 Release Notes
Change Notification Preferences
View Online
|
View Changes
[CONF] Apache Tapestry > Release Notes
Release Notes Page edited by Igor Drobiazko Changes (1) ... || Tapestry 5.3 | [Tapestry 5.3.0|Release Notes 5.3.0] | _Not yet released_ | || Tapestry 5.2 | [Consolidated Release Notes for 5.2|Release Notes 5.2] | *This is the current stable release* | || | [Release Notes 5.2.5] | Released 23 Mar 2011 | || | [Release Notes 5.2.4] | Released 15 Nov 2010 | || | [Release Notes 5.2.3] | Released 11 Nov 2010 | ... Full Content These release notes provide the details of the changes in each Tapestry version. Tapestry 5.3 Tapestry 5.3.0 Not yet released Tapestry 5.2 Consolidated Release Notes for 5.2 This is the current stable release Release Notes 5.2.5 Released 23 Mar 2011 Release Notes 5.2.4 Released 15 Nov 2010 Release Notes 5.2.3 Released 11 Nov 2010 Release Notes 5.2.2 Released 24 Oct 2010 Release Notes 5.2.1 Released 29 Sep 2010 Release Notes 5.2.0 Released 8 Aug 2010 Tapestry 5.1 Release Notes 5.1 Released Apr 23, 2009 Tapestry 5.0 Release Notes 5.0 Released Dec 2008 Change Notification Preferences View Online | View Changes
[CONF] Apache Tapestry > Release Notes 5.2.5
Release Notes 5.2.5 Page edited by Igor Drobiazko Changes (6) ... h3. Bug * [TAP5-1372|https://issues.apache.org/jira/browse/TAP5-1372] - BaseURLSource uses getLocalPort() rather than getServerPort() h3. Improvement * [TAP5-1040|https://issues.apache.org/jira/browse/TAP5-1040] - Allow HTML5 doctype to be printed * [TAP5-1208|https://issues.apache.org/jira/browse/TAP5-1208] - In development mode, Tapestry should "shadow" field & parameter values to instance variables, to assist with debugging * [TAP5-1346|https://issues.apache.org/jira/browse/TAP5-1346] - Fix broken links on new Web Site * [TAP5-1378|https://issues.apache.org/jira/browse/TAP5-1378] - Allow Delegate component to be used for creating in-template components h3. New Feature * [TAP5-742|https://issues.apache.org/jira/browse/TAP5-742] - Add optional component tracing comments to rendered output Full Content Version 5.2.5 is a maintenance release for 5.2.4. Bug TAP5-1372 - BaseURLSource uses getLocalPort() rather than getServerPort() Improvement TAP5-1040 - Allow HTML5 doctype to be printed TAP5-1208 - In development mode, Tapestry should "shadow" field & parameter values to instance variables, to assist with debugging TAP5-1346 - Fix broken links on new Web Site TAP5-1378 - Allow Delegate component to be used for creating in-template components New Feature TAP5-742 - Add optional component tracing comments to rendered output Change Notification Preferences View Online | View Changes
[CONF] Apache Tapestry > Release Notes 5.2.5
Release Notes 5.2.5 Page added by Igor Drobiazko Version 5.2.5 is a maintenance release for 5.2.4. Bug TAP5-1372 - BaseURLSource uses getLocalPort() rather than getServerPort() Improvement TAP5-1040 - Allow HTML5 doctype to be printed TAP5-1208 - In development mode, Tapestry should "shadow" field & parameter values to instance variables, to assist with debugging TAP5-1346 - Fix broken links on new Web Site TAP5-1378 - Allow Delegate component to be used for creating in-template components New Feature TAP5-742 - Add optional component tracing comments to rendered output Change Notification Preferences View Online
[CONF] Apache Tapestry > Release Notes
Release Notes Page edited by Bob Harner Comment: Converted to a table layout Changes (2) These release notes provide the details of the changes in each Tapestry version. h2. Tapestry 5.3 (unreleased) * [5.3.0|Release Notes 5.3.0] h2. Tapestry 5.2 * [5.2.4|Release Notes 5.2.4] -- 15 Nov 2010 * [5.2.3|Release Notes 5.2.3] -- 11 Nov 2010 * [5.2.2|Release Notes 5.2.2] -- 24 Oct 2010 * [5.2.1|Release Notes 5.2.1] -- 29 Sep 2010 * [5.2.0|Release Notes 5.2.0] -- 8 Aug 2010 h2. Tapestry 5.1 * [5.1|Release Notes 5.1] -- Apr 23, 2009 h2. Tapestry 5.0 * [5.0|Release Notes 5.0] -- Dec 2008 || Tapestry 5.3 | [Tapestry 5.3.0|Release Notes 5.3.0] | _Not yet released_ | || Tapestry 5.2 | [5.2 Consolidated release notes|Release Notes 5.2] | *This is the current stable release* | || | [Release Notes 5.2.3] | Released 11 Nov 2010 | || | [Release Notes 5.2.2] | Released 24 Oct 2010 | || | [Release Notes 5.2.1] | Released 29 Sep 2010 | || | [Release Notes 5.2.0] | Released 8 Aug 2010 | || Tapestry 5.1| [Release Notes 5.1] | Released Apr 23, 2009 | || Tapestry 5.0| [Release Notes 5.0] | Released Dec 2008 | Full Content These release notes provide the details of the changes in each Tapestry version. Tapestry 5.3 Tapestry 5.3.0 Not yet released Tapestry 5.2 5.2 Consolidated release notes This is the current stable release Release Notes 5.2.3 Released 11 Nov 2010 Release Notes 5.2.2 Released 24 Oct 2010 Release Notes 5.2.1 Released 29 Sep 2010 Release Notes 5.2.0 Released 8 Aug 2010 Tapestry 5.1 Release Notes 5.1 Released Apr 23, 2009 Tapestry 5.0 Release Notes 5.0 Released Dec 2008 Change Notification Preferences View Online | View Changes
[CONF] Apache Tapestry > Release Notes 5.2.1
Release Notes 5.2.1 Page moved by Bob Harner From: Apache Tapestry > Release Notes To: Apache Tapestry > Release Notes 5.2 Children moved Change Notification Preferences View Online
[CONF] Apache Tapestry > Release Notes 5.2.0
Release Notes 5.2.0 Page moved by Bob Harner From: Apache Tapestry > Release Notes To: Apache Tapestry > Release Notes 5.2 Children moved Change Notification Preferences View Online
[CONF] Apache Tapestry > Release Notes 5.2.2
Release Notes 5.2.2 Page moved by Bob Harner From: Apache Tapestry > Release Notes To: Apache Tapestry > Release Notes 5.2 Children moved Change Notification Preferences View Online
[CONF] Apache Tapestry > Release Notes 5.2.3
Release Notes 5.2.3 Page moved by Bob Harner From: Apache Tapestry > Release Notes To: Apache Tapestry > Release Notes 5.2 Children moved Change Notification Preferences View Online
[CONF] Apache Tapestry > Release Notes 5.2.4
Release Notes 5.2.4 Page moved by Bob Harner From: Apache Tapestry > Release Notes To: Apache Tapestry > Release Notes 5.2 Children moved Change Notification Preferences View Online
[CONF] Apache Tapestry > Release Notes 5.1
Release Notes 5.1 Page edited by Bob Harner Comment: Renamed for consistency with other Release Notes pages Changes (0) ... Full Content Contents Tapestry Version 5.1.0.5 Tapestry Version 5.1.0.4 Tapestry Version 5.1.0.3 Tapestry Version 5.1.0.2 Tapestry Version 5.1.0.1 Tapestry Version 5.1.0.0 Tapestry Version 5.1.0.5 Bugs Fixed TAP5-604 – ValidationMessages_da.properties contains invalid format strings TAP5-664 – Incorrect "legacy" URI specified in the templates documentation TAP5-665 – IE 6 on a tapestry SSL page complains about non-secure items (caused by blackbird js-logging component) TAP5-666 – Property _expression_ can not pass a boolean constant into a method TAP5-668 – BeanModel documentation should be more clear that a property must exist when using add(String). TAP5-670 – ParallelExecutorTest can't be compiled due to cast errors Improvements TAP5-214 – Document use of asset: and context: to reference assets directly from a template file TAP5-506 – Italian localization for DateField component TAP5-531 – Add cookbook documentation to show how to use the delegate component for switch-like behaviour TAP5-579 – Finnish internationalization is missing some of the keys in 5.1 TAP5-651 – If component documentation: identify the use of the p: namespace New Features TAP5-223 – Allow properties files (on classpath or in the context) to be used as SymbolProviders TAP5-580 – Add get() method to TestBase to allow read access to private fields of objects via reflection TAP5-601 – Add German translation for client-side _javascript_ messages Tapestry Version 5.1.0.4 Bugs Fixed TAP5-130 – Tapestry component report fails if the project's path name contains spaces TAP5-353 – Description of volatile parameter for the Grid component is misleading, should be clear that application is responsible for the tracking the row TAP5-500 – Small typo in javadoc comments for Cookies service. TAP5-501 – In the Component interface javadoc the sentence "This interface is likely to change without notice." should be deleted or the interface be moved to an internal package TAP5-524 – Published parameters exposed from embedded components not included in Component Reference TAP5-571 – Misplaced results in an inscrutable exception TAP5-613 – Returning a Link to a secure page from an ajax event handler method causes the redirect to be invalid if the event is sent from an insecure page TAP5-622 – Client ids should not contain the ':' character, as that can confuse WebKit-based browsers TAP5-631 – Contributed ApplicationInitializer not always executed when using tapestry-spring TAP5-640 – DOM manipulation during rendering can NPE TAP5-641 – Inherited parameters that are themselves inherited will appear null TAP5-644 – When using PageTester, an exception in the page is hidden by an exception rendering the exception report page (pt. 2) TAP5-646 – When Tapestry is combining _javascript_ files, it should check for a JS file that ends with an unterminated comment, and add the comment terminator TAP5-647 – Quickstart archetype should not include the tapestry-test dependency, as the Jetty embedded inside Selenium gets in the way of RunJettyRun inside Eclipse TAP5-648 – Tapestry should be more careful about where, inside the , it adds new elements TAP5-649 – Forms containing loop components which contain no form elements still encode into t:formdata hidden field TAP5-652 – Script tag is missing required attribute type TAP5-653 – Appending a context to an URL of the Index page results in too many slashes TAP5-659 – In some servlet containers, access to virtual assets can result in a GZIP-related exception TAP5-660 – Type coercion from String to DateFormat will always coerce using the server's default locale, rather than the current per-thread locale Improvements TAP5-274 – Application State Object is a misleading term; rename @ApplicationState to @SessionState TAP5-612 – URLRewriting should distinguish between incoming and outgoing requests TAP5-629 – Ensure blackbird console appears on top of other page elements TAP5-654 – Improve component classes documentation to be clearer about relationship between @Component and t:id TAP5-655 – Quickstart archetype should set the application version number to match the module version number TAP5-657 – The FieldFocusPriority enum should include an additional value, OVERRIDE, to indicate a manually focused field (with highest priority) TAP5-661 – A number of minor documentation typos New Features TAP5-624 – Support for _javascript_ callbacks on zone update TAP5-642 – Document how to configure Glassfish 2.1 to deploy Tapestry applications TAP5-662 – Component documentation should identif
[CONF] Apache Tapestry > Release Notes 5.3.0
Release Notes 5.3.0
Page edited by Howard M. Lewis Ship
Changes (2)
{html} Feature [
It is now possible to have Tapestry emit rendering comments; these are comments (such as {{}}) that can assist you in debugging markup output on the client-side. This is enabled for all requests using the configuration symbol {{tapestry.component-render-tracing-enabled}}, and can be added to any request by adding the query parameter {{t:component-trace=true}} to the URL. This will significantly increase the size of the rendered markup, but can be very helpful with complex layouts to determine which component was responsible for which portion of the rendered page.
[{html}
Full Content
It is now possible to have Tapestry emit rendering comments; these are comments (such as ) that can assist you in debugging markup output on the client-side. This is enabled for all requests using the configuration symbol tapestry.component-render-tracing-enabled, and can be added to any request by adding the query parameter t:component-trace=true to the URL. This will significantly increase the size of the rendered markup, but can be very helpful with complex layouts to determine which component was responsible for which portion of the rendered page.
Change Notification Preferences
View Online
|
View Changes
[CONF] Apache Tapestry > Release Notes 5.3.0
Release Notes 5.3.0
Page edited by Josh Canfield
Comment:
Added note about generic properties
Changes (2)
{html} Feature [
It is now possible to have Tapestry emit rendering comments; these are comments (such as {{}}) that can assist you in debugging markup output on the client-side. This is enabled for all requests using the configuration symbol {{tapestry.component-render-tracing-enabled}}, and can be added to any request by adding the query parameter {{t:component-trace=true}} to the URL. This will significantly increase the size of the rendered markup, but can be very helpful with complex layouts to determine which component was responsible for which portion of the rendered page.
[{html}
Full Content
Feature
[TAP5-742] - Add optional component tracing comments to rendered output
It is now possible to have Tapestry emit rendering comments; these are comments (such as {{}}) that can assist you in debugging markup output on the client-side. This is enabled for all requests using the configuration symbol {{tapestry.component-render-tracing-enabled}}, and can be added to any request by adding the query parameter {{t:component-trace=true}} to the URL. This will significantly increase the size of the rendered markup, but can be very helpful with complex layouts to determine which component was responsible for which portion of the rendered page.
[TAP5-1389] - Access properties of generic page and component fields
Change Notification Preferences
View Online
|
View Changes
[CONF] Apache Tapestry > Release Notes 5.3.0
Release Notes 5.3.0
Page edited by Howard M. Lewis Ship
Changes (2)
It is now possible to have Tapestry emit rendering comments; these are comments (such as {{}}) that can assist you in debugging markup output on the client-side. This is enabled for all requests using the configuration symbol {{tapestry.component-render-tracing-enabled}}, and can be added to any request by adding the query parameter {{t:component-trace=true}} to the URL. This will significantly increase the size of the rendered markup, but can be very helpful with complex layouts to determine which component was responsible for which portion of the rendered page.
Full Content
It is now possible to have Tapestry emit rendering comments; these are comments (such as ) that can assist you in debugging markup output on the client-side. This is enabled for all requests using the configuration symbol tapestry.component-render-tracing-enabled, and can be added to any request by adding the query parameter t:component-trace=true to the URL. This will significantly increase the size of the rendered markup, but can be very helpful with complex layouts to determine which component was responsible for which portion of the rendered page.
Change Notification Preferences
View Online
|
View Changes
[CONF] Apache Tapestry > Release Notes 5.3.0
Release Notes 5.3.0 Page added by Howard M. Lewis Ship Change Notification Preferences View Online
[CONF] Apache Tapestry > Release Notes
Release Notes Page edited by Howard M. Lewis Ship Changes (1) These release notes provide the details of the changes in each Tapestry version. h2. Tapestry 5.3 (unreleased) * [5.3.0|Release Notes 5.3.0] h2. Tapestry 5.2 ... Full Content These release notes provide the details of the changes in each Tapestry version. Tapestry 5.3 (unreleased) 5.3.0 Tapestry 5.2 5.2.4 – 15 Nov 2010 5.2.3 – 11 Nov 2010 5.2.2 – 24 Oct 2010 5.2.1 – 29 Sep 2010 5.2.0 – 8 Aug 2010 Tapestry 5.1 Release Notes Tapestry 5.0 Release Notes Change Notification Preferences View Online | View Changes
[CONF] Apache Tapestry > Release Notes
Release Notes Page edited by Bob Harner Comment: Links to 5.1 and 5.0 release notes Changes (4) Tapestry release notes, by release: These release notes provide the details of the changes in each Tapestry version. h2. Tapestry 5.2 * [5.2.4|Release Notes 5.2.4] -- 15 Nov 2010 * [5.2.3|Release Notes 5.2.3] -- 11 Nov 2010 ... * [5.2.1|Release Notes 5.2.1] -- 29 Sep 2010 * [5.2.0|Release Notes 5.2.0] -- 8 Aug 2010 h2. Tapestry 5.1 [Release Notes|http://tapestry.apache.org/tapestry5.1/release-notes.html] h2. Tapestry 5.0 [Release Notes|http://tapestry.apache.org/tapestry5.0/release-notes.html] Full Content These release notes provide the details of the changes in each Tapestry version. Tapestry 5.2 5.2.4 – 15 Nov 2010 5.2.3 – 11 Nov 2010 5.2.2 – 24 Oct 2010 5.2.1 – 29 Sep 2010 5.2.0 – 8 Aug 2010 Tapestry 5.1 Release Notes Tapestry 5.0 Release Notes Change Notification Preferences View Online | View Changes
