Modified: websites/production/tapestry/content/release-notes-53.html
==
--- websites/production/tapestry/content/release-notes-53.html (original)
+++ websites/production/tapestry/content/release-notes-53.html Mon May 13
18:12:26 2024
@@ -144,11 +144,11 @@
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, and also
review theHow to Upgrade
instructions.Contents/**/
+/*]]>*/
Breaking ChangesNew FeaturesSub-tasks CompletedBugs FixedImprovements MadeNew Features
ImplementedTasks
Completed
Breaking
ChangesTapestry now depends on Servlet API version 2.5
(prior releases worked with 2.4).Tapestry no longer supports the ability
to inject the component id into a String field. This was rarely (if ever) used
functionality that caused unwanted conflicts elsewhere. When a component needs
to know its component id, it may inject the http://tapestry.apache.org/5.3/apidocs/org/apache/tapestry5/ComponentResources.html;>ComponentResources
object, and invoke getCompleteId().Tapestry templates
without a !DOCTYPE are treated a bit differently in Tapestry 5.3; they
are treated as if they have the HTML5 doctype (!DOCTYPE
html). See further notes about component templates.Many classes and
interfaces that were deprecated in prior releases of Tapestry have been removed
in Tapestry 5.3.
See https://issues.apache.org/jira/browse/TAP5-1432;>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 @http://tapestry.apache.org/5.3/apidocs/org/apache/tapestry5/annotations/Import.html;>Import)@ApplicationState
annotation (replaced with @http://tapestry.apache.org/5.3/apidocs/org/apache/tapestry5/annotations/SessionState.html;>SessionState)"validateForm"
event triggered by Form component (replaced with "validate"
event)Code and constants related to page poolingIn
addition, some of the abstract base classes used with the tapestry-func library
have changed into interfaces; you will want to recompile, but may also need to
adjust your code,
depending on your compiler settings and use of the standard Java @Override
annotation.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 http://tapestry.apache.org/5.2/apidocs/org/apache/tapestry5/RenderSupport.html;>RenderSupport
environmental (replaced with the http://tapestry.apache.org/5.3/apidocs/org/apache/tapestry5/services/javascript/JavaScriptSupport.html;>JavaScriptSupport
environmental)The http://tapestry.apache.org/5.2/apidocs/org/apache/tapestry5/ajax/MultiZoneUpdate.html;>MultiZoneUpdate
object, replaced with http://tapestry.apache.org/5.3/apidocs/org/apache/tapestry5/services/ajax/AjaxR
esponseRenderer.html">AjaxResponseRendererClassFactory service
and ClassFab interface (replaced with the http://tapestry.apache.org/5.3/apidocs/org/apache/tapestry5/ioc/services/PlasticProxyFactory.html;>PlasticProxyFactory
service and http://tapestry.apache.org/5.3/apidocs/org/apache/tapestry5/plastic/PlasticClass.html;>PlasticClass
interface)The "suppress redirects" functionality, which allows
component event requests to respond directly with HTML, as in Tapestry
4.New FeaturesUnderscore.jsTapestry now bundles http://underscorejs.org/;
rel="nofollow">Underscore.js, a useful library for expressive functional
programming in the browser. It is used in no conflict mode, made
available as the T5._ object.User AlertsTapestry 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
