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 2013/05/28 17:02:20 UTC

[jira] [Resolved] (WICKET-4952) Wicket-CDI and o.a.w.Session.replaceSession() do not play nice.

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

Igor Vaynberg resolved WICKET-4952.
-----------------------------------

    Resolution: Won't Fix

this can be implemented by creating a custom scope anchored to wicket's Session instance. pull requests/patches welcome.
                
> Wicket-CDI and o.a.w.Session.replaceSession() do not play nice.
> ---------------------------------------------------------------
>
>                 Key: WICKET-4952
>                 URL: https://issues.apache.org/jira/browse/WICKET-4952
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket-cdi
>    Affects Versions: 6.3.0, 6.4.0
>            Reporter: Dominik Drzewiecki
>            Assignee: Igor Vaynberg
>
> As CDI session-scoped beans are bound to the session, invoking o.a.w.Session.replaceSession() results in destoroying HttpSession and all bound beans. Maybe we could provide some hack to workaround this so that the beans wo't get flushed and be rebound to the newly created HttPSession?
> It is an evident servlet APIs shortcoming; it definitely lacks some more standard replaceSession() in its API.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira