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 2009/02/02 08:29:59 UTC

[jira] Closed: (WICKET-2046) wicket-guice do not work correctly when the application is redeployed with persistent sessions

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

Igor Vaynberg closed WICKET-2046.
---------------------------------

    Resolution: Duplicate

> wicket-guice do not work correctly when the application is redeployed with persistent sessions
> ----------------------------------------------------------------------------------------------
>
>                 Key: WICKET-2046
>                 URL: https://issues.apache.org/jira/browse/WICKET-2046
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket-guice
>    Affects Versions: 1.4-RC1
>            Reporter: Adriano dos Santos Fernandes
>         Attachments: guicetest.tar.gz
>
>
> The way wicket-guice (or rather, wicket-ioc) manages the typestore make it not work correctly when the application is redeployed with persistent sessions.
> When a proxy need to be retrieved from the typestore, before an object of the same type was being injected, GuiceProxyTargetLocator.locateProxyTarget() is called but the type is not present on the application typestore. See, it's added to the typestore in GuiceProxyTargetLocator constructor.

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