Migration to Wicket 7.0Page edited by Martin GrigorovChanges (6)
Full ContentMigrating to Wicket 7.0EnvironmentWicket 7.0 requires at least Java 7Wicket 7.0 requires Servlet 3.0The HTTP response is not flushed automatically when the request is started in asynchronous mode. WICKET-5152This is an improvement in Wicket 7.0 which should not affect any application migrating from Wicket 6.x. But if you use Servlet 3.0's AsyncContext in IResource in Wicket 7 then make sure that your code flushes the http response after completing the request.
Change Notification Preferences
View Online
|
View Changes
|
Add Comment
|
- [CONF] Apache Wicket > Migration to Wicket 7.0 confluence
- [CONF] Apache Wicket > Migration to Wicket 7.0 confluence
- [CONF] Apache Wicket > Migration to Wicket 7.0 confluence
- [CONF] Apache Wicket > Migration to Wicket 7.0 confluence
- [CONF] Apache Wicket > Migration to Wicket 7.0 confluence
- [CONF] Apache Wicket > Migration to Wicket 7.0 confluence
- [CONF] Apache Wicket > Migration to Wicket 7.0 confluence
- [CONF] Apache Wicket > Migration to Wicket 7.0 confluence
- [CONF] Apache Wicket > Migration to Wicket 7.0 confluence
- [CONF] Apache Wicket > Migration to Wicket 7.0 confluence
- [CONF] Apache Wicket > Migration to Wicket 7.0 confluence
- [CONF] Apache Wicket > Migration to Wicket 7.0 confluence