You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Ate Douma (JIRA)" <ji...@apache.org> on 2008/04/06 15:13:25 UTC

[jira] Assigned: (WICKET-1478) AbortWithWebErrorCodeException in onBeforeRender causes WicketRuntimeException

     [ https://issues.apache.org/jira/browse/WICKET-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ate Douma reassigned WICKET-1478:
---------------------------------

    Assignee: Johan Compagner  (was: Ate Douma)

Johan,

I don't have time to evaluate this right now: this is something too tricky to be able to review by looking at the code itself. I need to test this out in the portal to be sure what happens.
What I'm curious about though is: why do you "reset" the Application to previous? Why can't you just clear it properly (e.g. setting the threadlocals really to null) instead?

I'm willing to test this out and see how it works when running as a portlet, but it'll have to wait until after the ApacheCon (so next week the earliest).
For now, you're changes should be fine for plain webapps as the default non-portlet RequestContext instance doesn't keep any state anyway (the PortletRequestContext does however).

> 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: Johan Compagner
>            Priority: Minor
>             Fix For: 1.3.4
>
>         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.