I think there are many ways to fix this, ranging from easy to complex.

The easiest one: either catch it in a IRequestCycleListener (in
onException), and “fix” the request handler by stripping the
pageAndComponent info from it
Next option: override wicket’s exception mapper (see
DefaultExceptionMapper), and catch/fix it there.

Since this is a common issue for you, I’d got with a request cycle listener
since it’s quite easy to plug in:
- catch ComponentNotFoundException
- check if the request handler is a ListenerInterfaceRequestHandler
- return a BookmarkablePageRequestHandler or a RenderPageRequestHandler,
depending on the type of page that was being rendered (stateless,

Good luck.

Met vriendelijke groet,
Kind regards,

Bas Gooren

Op 29 juni 2018 bij 11:50:27, Korbinian Bachl (
korbinian.ba...@whiskyworld.de) schreef:


I've got some problems with 404/ 500 error codes in my wicket app that
happen to come from the past... Now, when wicket makes any url for a
component this one gets added to the path, e.g.:

So when time goes by and the component name changes to e.g.: inputForm3 and
one then calls the above URL wicket annoys with an 500 error...
(attention: it is also related to the fact if there is an active session or
there is not! - happy debugging !)


Component 'brix-tile-24:form' has been removed from page.


(error from my app - u get a bit different one from the wicket examples app
if you manually change the component info part - sometimes just an 404,
sometimes 500)

So, how can this be fixed that instead of giving us this 500er error in
live systems that wicket should just ignore the problem? I mean failing in
dev is OK but in deploy? So basically wicket shall treat it as



IMHO the problem here is in ListenerRequestHandler at 164:

if ((component == null && !freshPage) || (component != null &&
component.getPage() != page))
throw new ComponentNotFoundException("Component '" + getComponentPath()
+ "' has been removed from page.");

so we know there is no component and then wicket goes berserk and throws
it... Problem arises with many URLs indexed anywhere on the web and
pointing to ones page as well as bookmarked pages from users - they have
the old component info in the paths and there is no way to remove that!


To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Reply via email to