[CONF] Apache Wicket > Migration to Wicket 6.0

[confluence]

Migration to Wicket 6.0 Page edited by Martin Grigorov Comment: Add a note that AjaxRequestTarget is an interface now Changes (1) ... For more information read [Wicket Ajax|https://cwiki.apache.org/confluence/x/NK2oAQ] h4. AjaxRequestTarget is an interface o.a.w.ajax.AjaxRequestTarget is an interface now with a default implementation o.a.w.ajax.AjaxRequestHandler. This way it will be possible to replace it with a different implementation, or mock/spy it in tests. This change required to refactor AjaxRequestTarget.get() too. The replacement code is: {code} AjaxRequestTarget target = requestCycle.find(AjaxRequestTarget.class); {code} RequestCycle.find(Class<? extends IRequestHandler>) can be used to find the currently running or a scheduled IRequestHandler for other types too. h3. IHeaderResponse, including decorators and filters ... Full Content Migrating to Wicket 6.0 Environment Repeaters Form Processing Validation Ajax Use JQuery as a backing library for Wicket Ajax functionality AjaxRequestTarget is an interface IHeaderResponse, including decorators and filters Order of Header contributions and wicket:head package.properties renamed to wicket-package.properties List of renamed classes and methods Refactorings o.a.w.IComponentSource and o.a.w.ComponentSourceEntry are removed IInitializers are initialized before Application#init() Environment Wicket 6.0 requires at least Java 6 Repeaters `IDataProvider` was converted to using `long` instead of `int` to better line up with JPA and other persistence frameworks. This has caused a rather large cascade of `int` to `long` changes all over the repeater packages (WICKET-1175). Form Processing Validation `StringValidator` will add the `maxlen` attribute if added to a component attached to an input tag `AbstractValidator` has been removed `ValidationError` now makes creating standard error keys (classname and classname.subtype) easier Most validators provide a `decorate(ValidationError, Validatable)` method for overriding how they report errors Ajax Use JQuery as a backing library for Wicket Ajax functionality Apache Wicket needed to improve the implementation of its _javascript_ libraries used for Ajax functionality (wicket-ajax.js and wicket-event.js) by using any of the bigger _javascript_ libraries and delegate to it the handling of the differences in the browsers (DOM, events, Ajax, ...). After a discussion in the mailing lists the Wicket team decided to use JQuery for that. For more information read Wicket Ajax AjaxRequestTarget is an interface o.a.w.ajax.AjaxRequestTarget is an interface now with a default implementation o.a.w.ajax.AjaxRequestHandler. This way it will be possible to replace it with a different implementation, or mock/spy it in tests. This change required to refactor AjaxRequestTarget.get() too. The replacement code is: AjaxRequestTarget target = requestCycle.find(AjaxRequestTarget.class); RequestCycle.find(Class<? extends IRequestHandler>) can be used to find the currently running or a scheduled IRequestHandler for other types too. IHeaderResponse, including decorators and filters IHeaderResponse has been rewritten to render HeaderItems. All render* methods have been replaced by a single render(HeaderItem) method. HeaderItems can be instantiated using the factory methods in _javascript_HeaderItem, CssHeaderItem, OnDomReadyHeaderItem, OnLoadHeaderItem, OnEventHeaderItem and StringHeaderItem. For example, the following code in renderHead: response.renderCSSReference(new CssResourceReference(HomePage.class, "header.css")); response.renderJavaScriptReference(new _javascript_ResourceReference(HomePage.class, "page.js")); Needs to be replaced with: response.render(CssHeaderItem.forReference(new CssResourceReference(HomePage.class, "header.css"))); response.render(_javascript_HeaderItem.forReference(new _javascript_ResourceReference(HomePage.class, "page.js"))); Custom HeaderResponseDecorators and IHeaderResponseFilters also need to be adjusted for the changed methods. These classes now have only one method for rendering and filtering. Order of Header contributions and wicket:head The order of header contributions (including wicket:head) has changed with Wicket 6.0. By default components are visited child-first to contribute to the header. For every component, the header contribution from the markup (wicket:head) is rendered first, followed by header contributions done in the code. This means that headers contributed by the page are rendered at the bottom of the header, where they used to be at the top with Wicket 1.5. This way if the user application uses a component library and a component (or Page) from the library contributes some resource the user application has the possibility to override this contribution with its own one. package.properties renamed to wicket-package.properties The special resource bundle that can contain resources for a whole package has been renamed from package.properties to wicket-package.properties. This prefix will be used for all wicket resources which may collide somehow with resources provided by other frameworks. See WICKET-4211 List of renamed classes and methods Following the renames in subclasses is easier if the @Override annotations are present. IDE-s, like Eclipse, can be used to add missing @Override annotations before moving to wicket 6. Here's a table of deprecated classes and methods in Wicket 1.5 and the corresponding replacement in Wicket 6. Wicket 1.5 (deprecated) Wicket 6 (replacement) org.apache.wicket.behavior.SimpleAttributeModifier org.apache.wicket.AttributeModifier#replace(...) org.apache.wicket.request.Url#toAbsoluteString() org.apache.wicket.request.Url#toString(StringMode.FULL) org.apache.wicket.markup.html.IHeaderResponse org.apache.wicket.markup.head.IHeaderResponse org.apache.wicket.markup.html.internal.HeaderResponse org.apache.wicket.markup.head.internal.HeaderResponse org.apache.wicket.resource.filtering.HeaderResponseContainerFilteringHeaderResponse org.apache.wicket.markup.head.filter.FilteringHeaderResponse org.apache.wicket.resource.filtering.HeaderResponseFilteredResponseContainer org.apache.wicket.markup.head.filter.HeaderResponseContainer org.apache.wicket.resource.filtering.* org.apache.wicket.markup.head.filter.* Refactorings HttpsMapper has been refactored to make subclassing easier o.a.w.IComponentSource and o.a.w.ComponentSourceEntry are removed These classes were used as placeholders for further optimizations in Component's size but were never finished. IInitializers are initialized before Application#init() All IInitializer classes configured in wicket.properties are initialized before the call to Application#init(). This way the application has the control to re-configure something that comes from external library. WICKET-4088 Change Notification Preferences View Online | View Changes | Add Comment