Page History

...

==> You can easily achieve that by registering an application wide IComponentResolver with app.getPageSettings().addComponentResolver(). In addition we'll support "queuing" components in the near future, which is kind of what you are looking at but not exactly. You can queue a component with a parent container but eventually it'll be added to the container providing the child markup. That way the hierarchy remains in sync.

Wicket should have native support for multiple homepages, or "multi homing"

Quite often your application has multipe home pages: front page (not logged in), login page, and possible mobile login page and other "home pages" for various purposes / use cases. The problem is that wicket 1.4.12 does not currently support multiple home pages "out-of-the-box". You can achieve support for multiple homepage, errorpage, etc. with quite lot of work, but it would be beneficial to have it out-of-the-box.

MartinG: isn't that already supported ?

...

and in 1.5 you can use a request mapper to intercept the root url and return whatever page you want.

MartinM: Multi homing is not properly supported in many cases, for example assuming user's session timeouts -> what homepage to redirect him to?

Modal window built-in

Modal window capability should be built in such that coder don't need to insert <div wicket:id=modal-window-placeholder/>. It seems very futile. It should be enough to just override "isUsingModalWindow" in component hierarchy and the Wicket will provide one. Modal window implementation can be some interface, abstract one, or current one.

...

Coming in Wicket 1.3.1 WICKET-1272

Window scope

this will basically replace PageMap and allow users to store per browser tab/window attributes

Pagemaps/windows were dropped from 1.5+ in favor of simpler page versioning mechanics.

JDK-1.5 support

• Generify models
• Annotation for mounting a bookmarkable page - done in wicketstuff-annotation
• Use varargs, for instance (a bad example) MarkupContainer#add(Component) -> MarkupContainer#add(Component...)
• Take advantage of new classes (java.util.concurrent, LinkedHashMap that can be used as an LRUMap, etc) to remove some of the wicket.util classes

...

Support jsr 286 portlet specification:

• -* http://jcp.org/aboutJava/communityprocess/pfd/jsr286/index.html-

-See this issue for Portlet 2.0 related issues: -
-https://issues.apache.org/jira/browse/WICKET-1620-
Update: Portlet support has been dropped for Wicket 1.5 WICKET-2976

...

Using the pagemap isn't very elegant and passing in the current page isn't always convenient.

Make Validators more flexible

• let validators be a behavior to contribute to the markup (eg. maxlength attribute for <input>) Done
• let validators use IModel instead/in addition to fixed values (in 1.5 see ivalidatable#getmodel() in 1.4 see imodelawarevalidatable to which validtable in validators can be cast)

Make JavascriptStripper more flexible

...