Hi, This is the behavior since https://issues.apache.org/jira/browse/WICKET-4594 As the ticket explains the problem was that *all* parameters for the Ajax request were assumed to be the PageParameters for the freshly created page. And this causes other problems ... :-/
On Wed, Oct 10, 2012 at 11:11 AM, Phill <[email protected]> wrote: > Wicket 6.1.1 - I'm mounting a bookmarkable page in my Application with a > named parameter: > > mountPage("/user/${userId}", UserPage.class); > > If I click an expired (session timeout) AjaxLink on the page /user/ABC it is > detected and handled by the RequestHandler but the named parameter is not > passed to the recreated page, redirecting to /user/?1 and not /user/ABC > > 2012-10-10 08:50:30,924 [http-thread-pool-8009(3)] DEBUG > o.a.wicket.core.request.handler.ListenerInterfaceRequestHandler - A > ListenerInterface '[RequestListenerInterface name=IBehaviorListener, > method=public abstract void > org.apache.wicket.behavior.IBehaviorListener.onRequest()]' assigned to > 'content:addCommentLink' is executed on an expired stateful page. Scheduling > re-create of the page and ignoring the listener interface… > > Is this the expected behaviour or a bug? > -Phill > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
