This page lists the tasks the Wicket team agreed to implement for Wicket 7.0.
Ideas for Wicket 7.0 list some more ideas but to add a task in the Roadmap it has to be discussed first in the dev mailing list. Ideas with attached patch in Jira ticket or Pull Request have a bigger chance to be included in the Roadmap.
Java 7 as a minimum
Java 7 has nice support for generics, better annotations, and Java 6 is reaching its end of life pretty soon.
Assignee: mgrigorov
Status: Not started
Jira:
Generics for org.apache.wicket.Component
Using Java 7 will allow to use the "diamonds operator", i.e.
Component<Entity> c = new SomeComponent<>("id", model);
Assignee: mgrigorov
Status: Not started
Jira:
Servlet 3 as a minimum
While we opted to not require servlet 3 for wicket 6, it has bitten us a couple of times solving issues in wicket 6. Servlet 3 has been out for ages, so we should move with the times.
Assignee: mgrigorov
Status: Not started
Jira:
Tickets in Jira with "Fix Version" = 7.0
PageParameters improvements
- read-only
- make it possible to differentiate between named indexed parameters and query string ones.
See WICKET-4594, http://markmail.org/thread/cc7yjwshqugj4wic, WICKET-4441
Assignee: mgrigorov
Status: Not started
Minor API cleanups
- Rename renderHead(HtmlHeaderContainer) https://issues.apache.org/jira/browse/WICKET-4964
Assignee: mgrigorov
Status: Not started
Jira: WICKET-4964
API Tweaks
SimpleFormComponentLabel should output the "required" class just like wicket:for
ajaxbehavior#updateAjaxAttributes() should get component passed in
otherwise referencing the component as needed in throttle settings is annoying
queryField.add(new AjaxFormComponentUpdatingBehavior("onkeydown") { protected void updateAjaxAttributes(AjaxRequestAttributes attributes) { attributes.setThrottlingSettings(new ThrottlingSettings(queryField.getMarkupId(), Duration.seconds(1))); ----------------------------------------------------------------------------^
throttling settings should be mutable to make it easier to override just the duration without having to figure out an id
JavaScriptResourceReference#getDependencies() should return an appendable List
so we can do
class MyReference extends JavascriptReference { getDependencies() { List<?> list=super.getDependencies(); list.add(...); return list; } }