Wicket 1.5 jetzt raus
Siehe .
Most notable changes
With this release the Wicket team has revised many of its internals. A short list:
- HTML5 components added:
EmailTextField,NumberTextField,UrlTextFieldandRangeTextField- New inter-component events (explained below)
- Minimum required servlet API is servlet-api 2.5
- All standard validators now extend
Behaviorto allow for client side validationsIBehaviorhas been removed andAbstractBehaviorhas been deprecated, you should now extendBehaviorinstead- Simplified the request cycle processing and made it more extensible
URLhandling is now in one place- Wicket’s rendering code has been greatly simplified
- Improved browser caching support
- ClientSideImageMap replaces old ImageMap
- Better support for running behind proxies with
x-forwarded-forheader- Request cycle listeners make it easier to integrate frameworks in your Wicket application
- Consistent naming: methods with
Javascriptin the name have been renamed to use proper capitalization:JavaScript- Switching to HTTPS is as simple as configuring a new root mapper to make Wicket HTTPS aware and annotating a page with
@RequireHttpsA longer list of changes and improvements can be found in our migration guide.
2 Kommentare
Christian Ullenboom ·
Wicket benötigt einen Servlet-Container mit 2.5, aber das in in der Regel kein Problem, da alle modernen Containern 2.5 sind. Wenn man einen alten Container hat, läuft es einfach nicht, weil Methoden fehlen.
Nizar ·
Hallo Christian, die neuste Wicket-version 1.5.3 hat, wie du auch schreibst (Minimum required servlet API is servlet-api 2.5 ), Abhängigkeit zu dem Servlet-api 2.5. Welche min-requirements sind das? Könnte ich Wicket 1.5.3 mit Servlet-api 2.4 nutzen? was würde dabei kaputtgehen? Danke im Voraus Nizar
Die bisherigen Kommentare wurden aus WordPress übernommen. Neue Kommentare sind derzeit geschlossen.