Siehe http://wicket.apache.org/2011/09/07/wicket-1.5-released.html.
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
- URL handling 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 @RequireHttps
A longer list of changes and improvements can be found in our migration guide.
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
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.