This page lists ideas what can be improved for Wicket 7.0.

Ajax back button support

Igor has already started something about this at his GitHub

Better stateless support

• add more stateless components (stateless versions of existing components)
• adopt Ajax stateless behaviors
• ...

Implement JAX-RS on top of Wicket IResource

Crazy, but why not ...

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

Removal of auto-components

Auto components caused some problems due to their special lifecycle - they appear only during the rendering process. This will simplify component queueing, resolvers+auto components, problems with enclosures, ...

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.

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.