You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Igor Vaynberg (JIRA)" <ji...@apache.org> on 2010/08/25 02:56:17 UTC

[jira] Resolved: (WICKET-2945) Filters and a application have different contexts

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

Igor Vaynberg resolved WICKET-2945.
-----------------------------------

      Assignee: Igor Vaynberg
    Resolution: Invalid

your problem is that there is literally no session because wicket had yet no need to start one. add this to the end of your homepage constructor and it will work fine:  getSession().bind();

> Filters and a application have different contexts
> -------------------------------------------------
>
>                 Key: WICKET-2945
>                 URL: https://issues.apache.org/jira/browse/WICKET-2945
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.4.9
>            Reporter: Dmitry Rodiontsev
>            Assignee: Igor Vaynberg
>         Attachments: sandbox.log, sandbox.zip
>
>
> I'm not familiar with multi-threaded applications, but in the Wicket 1.4.7 my example works correctly. Now it's broken.
> Looks like filter and wicket application lives in the different contexts and has different threads.
> Any thoughts on what is causing this problem?
> Thanks,
> Dmitry.

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