...
- TAP5-708 – Element.forceAttribute uses the element's namespace to match the attribute.
- TAP5-709 – Element.attribute(String name, String value) adds elements that already exist
- TAP5-804 – Element#addClassName can create an additional new 'class' attribute
- TAP5-921 – Properties defined in an Interface are not exposed by PropertyAccess for abstract classes that do not directly implement the methods
- TAP5-1287 – Some services require a notification that they have been reloaded, so they can clean up external dependencies
- TAP5-1293 – Whitespaces in SymbolConstants.SUPPORTED_LOCALES cause that locales are not persised
- TAP5-1294 – Validation macros do not work when used in @Validate annotation
- TAP5-1297 – Client-side validation of @Pattern is broken
- TAP5-1303 – Linking a Form to a Zone will no longer work unless the Form contains validated fields
- TAP5-1304 – When using PropertyShadowBuilder to build a service, if the property is null, an immediate exception is needed (rather than a NullPointerException)
- TAP5-1309 – When using a MultiZoneUpdate, Tapestry will clear the referenced zone
Improvements Made
- TAP5-538 – Add the facility to optionally disable on-focus-change triggered validation while retaining the on-form-submit validation
- TAP5-874 – Form component should be able to render a secure URL even on an insecure page
- TAP5-1272 – New annotations @Decorate and @Advise to identify methods that decorate or annotate services
- TAP5-1291 – Extend Link with new methods for producing absolute URLs (that include scheme, hostname, etc.)
- TAP5-1295 – Simplify connecting a link or form to an (enclosing) Zone
- TAP5-1298 – BeanBlockContribution should be split into two sub-classes: EditBlockContribution and DisplayBlockContribution
- TAP5-1300 – Define a special CSS class to prevent a client-side form from submitting normally (for Ajax use cases)
- TAP5-1306 – Additional method for Link: addParameterValue(String,Object) that uses ContextPathEncoder to encode object value to a string
- TAP5-1314 – SeleniumTestCase should expose the underlying CommandProcessor, to allow execution of commands not defined by the Selenium interface
- TAP5-1315 – Allow individual SeleniumTestCases to run w/o configuring SeleniumLauncher
New Features Added
- TAP5-1299 – Option to disable live service reloading via a JVM system property
...