Page History

{scrollbar}

...

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. Most users will not be affected by this unless they relied on Tapestry's dependency on Javassist.

ClientBehaviorSupport Functionality Removed

This service collected details about zone usage, including the client-side behavior associated with FormFragments. This interface is only kept for binary compatibility in Tapestry 5.4; the implementation no longer does anything but throw exceptions and will be removed in 5.5 or later.

FormInjector Removed

The FormInjector component was removed; it was intended for use only inside the AjaxFormLoop component (which was rewritten in 5.4 and no longer uses FormInjector). FormInjector was not widely used elsewhere, if it was used at all.

MarkupWriterFactory API

...

Changed

The MarkupWriterFactory interface has a couple of 3 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. As noted in the Javadocs, use JavaScriptSupport directly instead.

Injected Scripts at Bottom

...

Prior releases of Tapestry primarily organized client-side logic in terms of JavaScript libraries. These libraries can be declaratively imported into the page (either during a full-page render, or during an Ajax partial page update). In addition, libraries can be combined together into stacks, which (in a production application) are combined into a single virtual asset.

The library approach is fundamentally limited in a number of ways, including namespace pollution and dealing with dependencies between libraries. Tapestry 5.4 introduces a parallel mechanism, based on RequireJS and the Asynchronous Module Definition as a way to speed up initial page load and organize client-side JavaScript in a more expressive and maintainable way.

Client-side API for invoking server-side events

Tapestry 5.4.2 adds an API which makes it easy for server-side events to be invoked from JavaScript. In the server-side, you first need to annotate the event handler methods you want exposed with the new @PublishEvent annotation. Then, in JS, all you need to do is to call the t5/core/ajax function with the server-side event name/type in the url parameter and with an options parameter containing an element property, be it null or specifying an DOM element to be used as the starting point for finding the event information. More details in the Ajax and Zones page.

{scrollbar}