As I have reported a couple of weeks ago (but can't find the message any
more for a follow-up), Wicket shows an ugly internal-error page if one
somehow modified the stateful URLs, e.g.
http://localhost:8080/?wicket:interface=:8
Following exception is logged:
I haven't tried such a thing yet, but the last chapter of Wicket in
Action describes how to do such things.
Here's the example they give for responding with different error pages
for specific errors.
public class CheesrRequestCycle extends WebRequestCycle {
public
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
--
View this message in context:
http://www.nabble.com/InvalidUrlException---how-to-show-404-page-tp25712108p25712450.html
Sent from the Wicket
I think it should be possible to have the webserver deliver the standard
404 page by throwing AbortWithWebErrorCodeException
You can hook in at WebRequestCycleProcessor#respond(RuntimeException
e, RequestCycle requestCycle)
and throw the mentioned exception. Works find just like this in our
Hi Linda, Alex and Jonas,
Thank you for your answers.
Just for the records: I'm now setting the internal error page in
WebApplication.init() as Alex suggested and override
WebApplication.newRequestCycle(Request, Response) to return a subclass of
WebRequestCycle which overrides
-h...@wicket.apache.org
--
View this message in context:
http://www.nabble.com/InvalidUrlException---how-to-show-404-page-tp25712108p25726016.html
Sent from the Wicket - User mailing list archive at Nabble.com
