hmm that also doesn't fix it completely i am also diving into this, it is pretty complex now when you also take the wicket servlet into account :(
On 8/29/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > > I think that fixed it. > > Eelco > > On 8/28/07, Jan Vermeulen <[EMAIL PROTECTED]> wrote: > > > > I'll do that. > > > > Jan. > > > > Matej Knopp-2 wrote: > > > > > > That's not good. Can you please create a jira issue for this? > > > > > > -Matej > > > > > > On 8/28/07, Jan Vermeulen <[EMAIL PROTECTED]> wrote: > > >> > > >> > > >> 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(). > > >> > > >> Can this be fixed ? > > >> > > >> Jan. > > >> -- > > >> View this message in context: > > >> > http://www.nabble.com/WicketServlet-no-longer-sets-application-on-current-thread-tf4342913.html#a12371848 > > >> Sent from the Wicket - Dev mailing list archive at Nabble.com. > > >> > > >> > > > > > > > > > > -- > > View this message in context: > http://www.nabble.com/WicketServlet-no-longer-sets-application-on-current-thread-tf4342913.html#a12372441 > > Sent from the Wicket - Dev mailing list archive at Nabble.com. > > > > >
