[jira] Assigned: (WICKET-903) WicketServlet no longer sets application on current thread

["Johan Compagner (JIRA)" <ji...@apache.org>]

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

Johan Compagner reassigned WICKET-903:
--------------------------------------

    Assignee: Eelco Hillenius

eelco broke it, so he know ofcourse exactly how to fix it.

> WicketServlet no longer sets application on current thread
> ----------------------------------------------------------
>
>                 Key: WICKET-903
>                 URL: https://issues.apache.org/jira/browse/WICKET-903
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.3.0-beta3, 1.3.0-beta4, 1.3.0-rc1, 1.3.0-final, 1.4.0-alpha, 1.3.1
>         Environment: Windows, OSGI-platform
>            Reporter: Jan Vermeulen
>            Assignee: Eelco Hillenius
>            Priority: Critical
>
> The last changes made to WicketFilter (move Application.set(webApplication) from doGet() to doFilter()) have  a side effect: if working with WicketServlet (due to OSGI), the application is no longer set on the current thread, because it was moved to doFilter().
> Possible fixes:
> * move Application.set() in WicketFilter back to doGet(), at the start if that's early enough
> * expose the webApplication property, and add an extra Application.set() in the doGet() of WicketServlet

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.