Our application uses an implementation of IRequestCycleListener to redirect users to a custom error page with contextual information (which includes a reference to an external bug tracking system).
When the target page is also mounted in the application, we are seeing rather unexpected behavior: the custom error page is created as expected, but Wicket then tries to recreate the page by calling a default constructor (which exists), rendering the error page without the contextual information. Is this expected behavior, or is this a bug? I've created the following quickstart to illustrate the problem: https://github.com/jsteenbeeke/wicket-custom-mounted-errorpage-loses-context Sincerely, Jeroen Steenbeeke
