You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Martijn Dashorst (JIRA)" <ji...@apache.org> on 2008/06/22 15:17:47 UTC
[jira] Updated: (WICKET-1478) AbortWithWebErrorCodeException in
onBeforeRender causes WicketRuntimeException
[ https://issues.apache.org/jira/browse/WICKET-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martijn Dashorst updated WICKET-1478:
-------------------------------------
Fix Version/s: (was: 1.3.4)
1.3.5
> AbortWithWebErrorCodeException in onBeforeRender causes WicketRuntimeException
> ------------------------------------------------------------------------------
>
> Key: WICKET-1478
> URL: https://issues.apache.org/jira/browse/WICKET-1478
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.3.2
> Reporter: Michael Sparer
> Assignee: Ate Douma
> Priority: Minor
> Fix For: 1.3.5
>
> Attachments: quickstart404.jar
>
>
> Using custom error pages as described on http://cwiki.apache.org/WICKET/error-pages-and-feedback-messages.html, a wicket RTE gets thrown "There is no application attached to current thread [threadname]" when a AbortWithWebErrorCodeException is thrown in the onBeforeRender method of a WebPage. Note that this _only_ happens when using a custom error page defined in web.xml.
> See attached quickstart for the complete stacktrace (and my usecase)
> See also the mailinglist entry on http://www.nabble.com/Throw-AbortWithWebErrorCodeException-in-onBeforeRender-to16446341.html#a16473849
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.