Release Notes 5.3

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.

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

In 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 RenderSupport environmental (replaced with the JavaScriptSupport environmental)
ClassFactory service and ClassFab interface (replaced with the PlasticProxyFactory service and PlasticClass interface)
The "suppress redirects" functionality, which allows component event requests to respond directly with HTML, as in Tapestry 4.

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, using a debugger has been difficult with Tapestry 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.

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.

Form Cancelled Event

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.

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.

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 referenced by an event handler method (the Fromcomponent 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).

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 servlets or filters, as a way to prevent conflicts.

Improved Quickstart Archetype

The Maven quickstart archetype has been brought up to date, and now demonstrates several new bits of common useful functionality.

Whitelisted Pages

The new @WhitelistAccessOnly annotation marks a page as accessible only from white-listed clients; the rules for the whitelist are extensible. The default rule is that only access from localhost is on the white-list. Use this annotation on pages that may expose sensitive data, such as built-in application dashboards and the like.

Page Catalog

Tapestry applications now include a built-in "PageCatalog" page, which lists all the loaded pages of the application, with details about construction time and number of components. The page requires whitelist access (see above comment), and some functionality is only available in development mode. PageCatalog can be used to load all pages of your application, which is useful to quickly spot problems in your pages (especially useful when upgrading from a prior release of Tapestry).

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. In addition, Tapestry will now display a pop-up window containing the full exception report for a server-side error that occurs during an Ajax request.

JIRA Issues

Sub-task

Bug

[TAP5-5] -
[TAP5-7] -
[TAP5-8] -
[TAP5-9] -
[TAP5-16] -
[TAP5-17] -
[TAP5-19] -
[TAP5-21] -
[TAP5-26] -
[TAP5-31] -
[TAP5-35] -
[TAP5-36] -
[TAP5-38] -
[TAP5-40] -
[TAP5-115] -
[TAP5-137] -
[TAP5-218] -
[TAP5-763] -
[TAP5-832] -
[TAP5-845] -
[TAP5-875] -
[TAP5-877] -
[TAP5-891] -
[TAP5-922] -
[TAP5-998] -
[TAP5-1146] -
[TAP5-1227] -
[TAP5-1257] -
[TAP5-1331] -
[TAP5-1336] -
[TAP5-1339] -
[TAP5-1355] -
[TAP5-1366] -
[TAP5-1367] -
[TAP5-1368] -
[TAP5-1369] -
[TAP5-1372] -
[TAP5-1374] -
[TAP5-1383] -
[TAP5-1393] -
[TAP5-1408] -
[TAP5-1409] -
[TAP5-1418] -
[TAP5-1422] -
[TAP5-1423] -
[TAP5-1428] -
[TAP5-1429] -
[TAP5-1444] -
[TAP5-1448] -
[TAP5-1486] -
[TAP5-1491] -
[TAP5-1497] -
[TAP5-1500] -
[TAP5-1510] -
[TAP5-1527] -
[TAP5-1535] -
[TAP5-1546] -
[TAP5-1549] -
[TAP5-1551] -
[TAP5-1554] -
[TAP5-1555] -
[TAP5-1562] -
[TAP5-1563] -
[TAP5-1571] -
[TAP5-1576] -
[TAP5-1577] -
[TAP5-1578] -
[TAP5-1580] -
[TAP5-1585] -
[TAP5-1593] -
[TAP5-1596] -
[TAP5-1598] -
[TAP5-1599] -
[TAP5-1605] -
[TAP5-1608] -
[TAP5-1613] -
[TAP5-1614] -
[TAP5-1620] -
[TAP5-1629] -
[TAP5-1631] -
[TAP5-1632] -
[TAP5-1636] -
[TAP5-1643] -
[TAP5-1644] -
[TAP5-1647] -
[TAP5-1652] -
[TAP5-1656] -
[TAP5-1657] -
[TAP5-1670] -
[TAP5-1673] -
[TAP5-1675] -
[TAP5-1676] -

Dependency upgrade

[TAP5-1653] -

Improvement

[TAP5-2] -
[TAP5-27] -
[TAP5-44] -
[TAP5-46] -
[TAP5-55] -
[TAP5-58] -
[TAP5-65] -
[TAP5-76] -
[TAP5-83] -
[TAP5-96] -
[TAP5-98] -
[TAP5-99] -
[TAP5-113] -
[TAP5-117] -
[TAP5-167] -
[TAP5-170] -
[TAP5-171] -
[TAP5-172] -
[TAP5-174] -
[TAP5-175] -
[TAP5-176] -
[TAP5-178] -
[TAP5-180] -
[TAP5-183] -
[TAP5-189] -
[TAP5-198] -
[TAP5-199] -
[TAP5-203] -
[TAP5-204] -
[TAP5-450] -
[TAP5-455] -
[TAP5-606] -
[TAP5-650] -
[TAP5-683] -
[TAP5-741] -
[TAP5-743] -
[TAP5-840] -
[TAP5-853] -
[TAP5-888] -
[TAP5-933] -
[TAP5-939] -
[TAP5-941] -
[TAP5-980] -
[TAP5-1040] -
[TAP5-1184] -
[TAP5-1199] -
[TAP5-1208] -
[TAP5-1308] -
[TAP5-1310] -
[TAP5-1320] -
[TAP5-1323] -
[TAP5-1348] -
[TAP5-1350] -
[TAP5-1356] -
[TAP5-1361] -
[TAP5-1362] -
[TAP5-1378] -
[TAP5-1382] -
[TAP5-1389] -
[TAP5-1390] -
[TAP5-1396] -
[TAP5-1414] -
[TAP5-1419] -
[TAP5-1431] -
[TAP5-1450] -
[TAP5-1451] -
[TAP5-1458] -
[TAP5-1469] -
[TAP5-1473] -
[TAP5-1476] -
[TAP5-1482] -
[TAP5-1485] -
[TAP5-1489] -
[TAP5-1492] -
[TAP5-1495] -
[TAP5-1496] -
[TAP5-1508] -
[TAP5-1519] -
[TAP5-1521] -
[TAP5-1523] -
[TAP5-1538] -
[TAP5-1539] -
[TAP5-1547] -
[TAP5-1558] -
[TAP5-1564] -
[TAP5-1565] -
[TAP5-1567] -
[TAP5-1574] -
[TAP5-1581] -
[TAP5-1588] -
[TAP5-1591] -
[TAP5-1594] -
[TAP5-1597] -
[TAP5-1603] -
[TAP5-1621] -
[TAP5-1627] -
[TAP5-1628] -
[TAP5-1633] -
[TAP5-1637] -
[TAP5-1638] -
[TAP5-1639] -
[TAP5-1641] -
[TAP5-1649] -
[TAP5-1651] -
[TAP5-1665] -
[TAP5-1669] -
[TAP5-1674] -

New Feature

[TAP5-54] -
[TAP5-67] -
[TAP5-68] -
[TAP5-71] -
[TAP5-72] -
[TAP5-73] -
[TAP5-82] -
[TAP5-85] -
[TAP5-94] -
[TAP5-102] -
[TAP5-110] -
[TAP5-111] -
[TAP5-120] -
[TAP5-122] -
[TAP5-141] -
[TAP5-142] -
[TAP5-143] -
[TAP5-144] -
[TAP5-145] -
[TAP5-149] -
[TAP5-153] -
[TAP5-155] -
[TAP5-158] -
[TAP5-159] -
[TAP5-742] -
[TAP5-753] -
[TAP5-1385] -
[TAP5-1421] -
[TAP5-1472] -
[TAP5-1502] -
[TAP5-1528] -
[TAP5-1542] -
[TAP5-1543] -
[TAP5-1550] -
[TAP5-1572] -
[TAP5-1586] -
[TAP5-1587] -
[TAP5-1595] -
[TAP5-1609] -

Task

[TAP5-75] -
[TAP5-116] -
[TAP5-161] -
[TAP5-162] -
[TAP5-973] -
[TAP5-1286] -
[TAP5-1397] -
[TAP5-1402] -
[TAP5-1432] -
[TAP5-1514] -
[TAP5-1610] -

Test

[TAP5-1413] -

Remove deprecated methods of PerthreadManager service Remove old IOCSymbols class, and outdated constants from IOCConstants Remove proxy-related building method from ClassFabUtils, since moved to ClassFactory#createProxy() Remove @ApplicationState annotation, replaced with @SessionState Remove @IncludeJavaScriptLibrary and @IncludeStylesheet annotations, replaced by @Import Remove OptimizedApplicationStateObject, replaced with OptimizedSessionStateObject Remove PrimaryKeyEncoder (replaced by ValueEncoder) Remove "validateForm" event triggered by Form component (replaced with "validate" event) Remove ValidationMessagesSource, replaced with ComponentMessagesSource Remove code and constants related to page pooling Remove symbol for absolute URIs (now always absolute since 5.2) Remove SCRIPTS_AT_TOP from SymbolConstants Remove AbstractField.createDefaultParameterBinding() and AbstractTextField.defaultValue() Remove deprecated constants from FormInjector Remove Loop.volatile parameter (replaced with formState parameter in 5.1) Remove Element.getParent() Remove EndTagStyle.OMIT Remove ClasspathAssetAliasManager.toResourcePath() Remove Environment.getAccess() Remove deprecated methods from TapestryTestCase Remove deprecated methods from ClassTransformation Context lost in a form fragment in a property editor component Palette component error marker appears on the line below the component when validation fails. Application message catalog is only used when a not localized version is present Component event requests that fail should still send a redirect (to the exception report page) Error popups are not positioned well near the edges of the page Null value in RadioGroup returns the string "on" Clicking on autocomplete scrollbar in Internet Explorer clears results Misleading error message when a component sub-class invokes non-default constructor of parent component class When @Validate("required") is applied to a field whose type is primitive, the client-side JavaScript includes two invocations of Tapestry.Validator.required DateField Calendar component has scroll bar burn through During an Ajax update, using a "var:" binding prefix causes an exception indicating that the page is not rendering Only the last of multiple t:parameter components with the same name in the same grid are rendered, without an error message. Validation error bubble positioning should be different for checkbox and radio than for other types of fields Pop up error bubbles (for client side validation) do not interact properly with IE 6 select elements Component report doesn't list parameters inherited from classes outside the project org.hibernate.TransactionException thrown when a transaction is directly rolledback (outside of tapestry-hibernate) the tapestry banner image on the component reference index page and the component reference pages links to wrong pages Documentation for RenderSupport.addScriptLink() is invalid about where the included links go Hidden input field fails with coercion problem on empty value (patch incl) Informal Parameters are not allowed to have the value "" (the empty string) 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 Fade effect for error popups should be disabled in IE since it can't properly fade the images RequestImpl.getSession(true) is broken Allow a null or blank value to be supplied in Link.addParameter(), and render out the parameter name with the missing value 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 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) Binding a parameter whose type is primitive to null results in a difficult to understand NullPointerException Javascript error with IE Prototype still in 1.7 EnumValueEncoder should identify legal values when a non-matching string is passed to it for conversion Changed classes do not reload under Tomcat Provide a single extension point to provide a ValidationDecorator instance for both traditional and Ajax renders Threading issue with SessionStateObjects Tapestry must honor the position of added tags in the <head> relative to the <meta> tags, for IE compatibility ajaxExceptionHandler Method name typo The onFailure function provided to Tapestry.ajaxRequest does not always get invoked ExceptionUtils.findCause() does not use the same approach as ExceptionAnalyzer BaseURLSource uses getLocalPort() rather than getServerPort() Quickstart layout component uses deprecated IncludeStyleSheet annotation TypeCoercer should "promote" coercions to primitive types into coercions to the corresponding wrapper type Form component shoould push the BeanValidationContext into the Environment only after onPrepare() datefield popup does not have option to cancel datefield - cannot select same day in different month Image submits do not set the javascript submitting element value. java.util.ConcurrentModificationException when shutting down jmx server Selenium test failures attempt to take a screenshot, which fails on most browsers besides firefox When a parameter is bound but does not match a formal parameter, the exception should also include a list of formal parameter names PageTester does not call registry.performRegistryStartup or TapestryAppInitializer.announceStartup Index pages in subfolders should have precedence over start pages Example for org.apache.tapestry5.corelib.components.Errors uses invalid xml When Tapestry adds CSS and JS files to the page, it should ensure that CSS files are above any JavaScript files In Chrome the buttons in the Palette component do not appear greyed-out when disabled No error message upon exception calling initializer function with German locale Update ComponentClassResolve's JavaDocs The @Advise annotation limits advice to just a specific interface type BeanEditForm loses object found by onPrepare() during render When there's a type mismatch between a container component at the field with @InjectComponent, the type of the containing component should be part of the exception message TranslatorSource incorrectly annotated with @UsesConfiguration when it should now be @UsesMappedConfiguration (as of 5.2) ParameterWorker forces evaluation of default method, even if the parameter is bound by other means FormFragment change visibility/hide and remove event listeners should call event.stop() to prevent container fragments from also being hidden Tapestry fails on OpenJDK with a java.lang.reflect.GenericSignatureFormatError Property Expression Array Disallows null and this Tree leafs are not selectable Need configuration for queue size w/ ParallelExecutor; as is, limited to pool core size threads, rather than pool max size t5-console.js throws exception in Chrome for debug, info, and warn JPA Integration 5.3.0 with Primary Key Entity Classes Fails Duplication in operation trace when invoking certain methods When toggling the visibility of a form fragment, the effective visibility doesn't change until after the animation completes A Form with an event listener for "canceled" event can cause an NPE popping off a BeanEditContext from the Environment that wasn't pushed @InjectPage annotation can leak page instances from one locale to another Type org.apache.tapestry5.services.HttpError should be an allowed return value from Ajax action requests Tapestry should validate that component ids reference in event handler method names (or @OnEvent annotation) exist AlertManager service does the wrong thing if the Ajax request will terminate with a redirect Upgrade Selenium to 2.3.1 Template parsing of expansions can't handle map expressions tapestry-ioc establishes dependency on TestNG that brings much unwanted stuff into runtime classpath Mixin inherited from parent model does not inherit order Component Javadocs need clarification on encoder parameter being "required" Tml parsing expression error A Tree component that does not have a selection model bound should not track selections on the client or server Tapestry creates client ids for error popups containing the ':' character, which is problematic for some browsers (and some testing tools) When a submit component does not have a specific id, the default id "submit" collides ont the client side with the HTMLFormElement.submit() method, causing JavaScript errors when the form is submitted Tapestry does not compile using OpenJDK Restore ability to contribute a library mapping that includes the "/" character (as was possible in 5.1) Symbol tapestry.compatibility.unknown-component-id-check-enabled when set to false still acts as if true PerThreadOperationTracker uses a synchronized block with high thread contention template expansion no longer trims whitespace off the right side of the expansion Problem when inheriting annotated methods from a abstract superclass Environment should use the UnknownValueException class, for better reporting on the exception page Debug output includes [[invoking-method]] (i.e., missing message key) when invoking contribution methods Tapestry 5.2 property expressions supported references to public static fields of classes; this is not supported by 5.3 Tapestry 5.3 allows a subcomponent to define a parameter with the same name as a base component When an @InjectComponent annotation fails due to missing component, it should identify the class name and field for the injection Update dependencies to latest versions DateField customization Improve exception message for default field validation when value parameter is not bound. enable creation of custom "onException" event handler Palette component should support drag and drop of the options Persistence strategy should alternately be specified via an annotation on the persisted field Tapestry should be smarter about event handler methods refiring events with the same name Validate fields based on EJB annotations Provide decorators service matching based on annotations add a contructor with page class as parameter to BeanBlockContribution Component parameter report should document alternate types The TypeCoercer should be able to coerce String to Enum types, even without a specific contribution Frequently instantiated service implementations should have a specialized instantiation class created to prevent extra reflection calls Ordering with pre/post requisites could be simplified, improved Allow contributing whole page to BeanBlockSource Applications should support both secured or unsecured access based on initial access method Basic generics support should apply to parameters of event handler methods as well as getters and setters Filter out attributes with default value (from DTD) when parsing templates It should be possible to merge validation constraints from the @Validate annotation with those explicitly set via the validate parameter Allow Zone requests to be cancelled maintain querystring parameters during @Secure redirect from http to https Enable @Mixins annotation in component classes Support for optional validator constraints make an ClientPersistentFieldStorageImpl abstract class Include mention of webdefault.xml in tapestry-test page When re-rendering a page with form validation errors, error pop-ups should be presented to the user as with normal client-side validation Handling Exceptions in Components by replacing/returning another component Tapestry writes localization initialization information for DateField even when in locale "en" Palette should be able to determine the generic type of the List passed to it, and use that to create default bindings for the model and encoder parameters The email validator should include client-side validation Add rel="nofollow" to t:grid sort links Allow discarding of persistent field changes for specific strategy only Add Finnish translation to javascript messages (Translated messages attached.) Enhance form autofocus to accept fieldname as a value The Tapestry object should include an info() for logging to the console (as it already includes error(), debug(), etc.) CSS files should be automatically minimalized, like JavaScript files It is too much work to hide all T5 pages inside a virtual folder, for use in mixed-implementation deployments Support character references in tml files with HTML 5 Doctype Move away from Javassist The Tapestry.ErrorPopup client-side class should create the div/span as needed (not at page initialization) EnumValueEncoder will create a ValueEncoder even when there's a specific String->Enum type coercion Chinese localization for ValidationMessages_zh_CN Chinese localization for corelib components ValidationDecorator should be a service, rather than just a contributed object, to make it easier to override Allow HTML5 doctype to be printed m2eclipse update site changed ClassTransformation should include an API specifically for adding a component event handler to a component class In development mode, Tapestry should "shadow" field & parameter values to instance variables, to assist with debugging When an Ajax requests replies with the error page, Tapestry should present the contents in a popup window The Enum ValueEncoder should be case insensitive ServiceActivity improvements Change Quickstart Template to Match New Site Design Component report should accept multiple root packages TapestryFilter should allow sub-classes to specify additional module classes, not just ModuleDefs When contributing to a service configuration, values should be coerced to the correct type rather than rejected if not the correct type Tapestry should include a coercion from Flow to List Tapestry should provide coercions from String to JSONObject and JSONArray Allow Delegate component to be used for creating in-template components Tapestry should provide a coercion from Flow to boolean, that evaluates to true if the Flow is not empty Access properties of generic page and component fields Functional programming improvements Invocation class should provide access to the annotations placed on the method beeing invoked Add HOSTNAME symbol to SymbolConstants, use in BaseUrlSource Tapestry tests should be able to be run from more than just Jetty Quickstart should enable the Blackbird client-side console Component report should print information about deprecated components or deprecated parameters Form component should indicate that a form submission was canceled on the client side Mark tapestry.suppress-redirect-from-action-requests as deprecated, for removal in Tapestry 5.4 Allow for multiple application root packages by contributing additional LibraryMappings with empty virtual folder Running integration tests with Tomcat6Runner it should be possible to configure the application under test by providing a local context.xml file Deprecate MultiZoneUpdate, replace with an injectable service to collect zone updates Upgrade Prototype to 1.7 / Scriptaculous 1.9.0 Quickstart archetype should define a ProductionModeModule and DevelopmentModeModule with support inside web.xml Re-storage of session attributes at end of request should be configurable (can be set to off for non-clustered applications) New features for SeleniumTestCase Tapestry's property expression language should support map creation Link components should support easily adding request parameters to the generated link Reduce memory utilization of Tapestry page instances Ensure that all calls to invoke methods and constructors with dependencies are tracked with the OperationTracker JavaScriptSupport.addInitializerCall() should support JSONArray of function parameters, as RenderSupport does Dutch validation messages Optimize client-side URL rebuilding in IE 7 Optimize document scans used by Tapestry.FieldEventManager to not locate the label or icon until actually needed Tapestry should include built-in coercions from String to JSONObject and JSONArray FormFragment should allow more fine grained control over when to be considered "invisible" RenderSupport is used in Upload.java even though it has been deprecated It should be easier to make a series of contributions to an OrderedConfiguration so that the contributions are in sequential orderer Contributions to the ValueEncoderSource service should allow bare ValueEncoders, which can be coerced to ValueEncoderFactory Provide constants for available data types MarkupWriterImpl makes many, many defensive copies of its listener list French properties file for the kaptcha component tapestry-ioc should not depend on tapestry-json Provide edit block for Kaptcha component Update Italian local support Tapestry should omit stack frames related to the OperationTracker from exception report TypeCoercer currently uses Object -> String and String -> Boolean, there should be a direct coercion from Object -> Boolean for <t:if/> performance. Enable OperationTracker to produce debug trace of all operations Have Submit documentation explicitly state when the disabled attribute is evaluated Hardcoded value for "Dismiss All" in AlertManager Tapestry should use SoftReferences for page instances, rather than run a janitor thread to clean them up Reduce thread contention inside ComponentClassResolverImpl Missing danish translations The ValueEncoder for Hibernate entity types should encode transient instances as null rather than throw an exception ComponentClassResolver should allow "common package root name" of a single term, and not require two terms It should be possible for a LinkCreationListener to override Tapestry and make a Link secure or insecure after the fact Tapestry could create non-singleton services more efficiently Palette Documentation Add ServiceBinder.withSimpleId() that generates a service id from the implementation class name Add configurable limits on how long (in ms) or how many operations are allowed when rendering Split persistence strategy into two parts: where the data is stored (session, client, hidden fields, etc.) and duration (normal, flash, maybe others) Add ability to use Seam and Tapestry 5 together Add a Tree component in corelib Improve Groovy support in Tapestry JavaScript libraries should be automatically packed/minimalized Allow Blocks to render themselves initially Make Java Class optional for Rendering Pages Add a "hidden fields" parameter to BeanEditor and BeanEditForm Add a "default sort column" parameter to Grid component let make JSONObject secured Protect serialized object blobs from being tampered by external user Make Tapestry 5 ready for IDE content assistance Integrate scriptaculous Ajax.InPlaceEditor with Tapestry The ServiceActivityScoreboard should provide greater detail, including method invocation counts and elapsed times HTML Button component with Form support Add client-side column resizing to grid. TestBase should support creating new class mocks (using easymockclassextension), not just traditional interface mocks TextField should include a parameter that will render a "suffix" (that appears between the field itself and any error decoration icons) Add JPA-annotation-driven validator Way to simulate annotations on classes, fields and methods Tapestry is missing a BinaryStreamResponse for streaming binary data to the client @Persist("redirection") TapestryFilter should support HTTP 1.1 byte ranges Add optional component tracing comments to rendered output Provide some way to get the current page instance being rendered inside a service Provide support for JSR-330 Create a standard way to track messages to be presented to the user Provide basic integration with JPA 2 Make it easier to create JavaScript Stacks using a standard implementation with an OrderedConfiguration Tapestry-specific JavaDoc plugin that generates parameter documentation, etc. Support for skinning/theming Tapestry pages Introduce Tapestry schema in version 5_3 Provide a multiple selection component that renders check boxes for available selection options Discard unused page instances if not used within a certain period Introduce the Kaptcha component Provide support for Serbian locale Provide support for Macedonian locale Generate Maven archetype from within gradle builds Create Doxia APT Macro to make it easier to link to JavaDoc Replace Maven build with Gradle build Devise test stategy for DateField and other DHTML/JS intensive components The need for specific content in webdefault.xml file should be documented Identify and fix the issue that causes intermittent build failures Remove Maven APT files for documentation that has moved into the Confluence wiki Remove Tutorial source from SVN Remove deprecated Alias service (which was replaced in 5.1 with the simpler ServiceOverride service) Remove classes and methods deprecated in Tapestry 5.2 Upgrade YUICompressor dependency to latest, 2.4.6 Provide JavaDoc styling similar to Tapestry website's style Test to make sure the ability to give a multizoneupdate a String rather than a zone works

Release Notes 5.2

Release Notes

Release Notes 5.3.1

Page tree