[
https://issues.apache.org/jira/browse/EXTCDI-222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerhard Petracek resolved EXTCDI-222.
-------------------------------------
Resolution: Won't Fix
the issue is perfectly fine at MYFACES-3302. as discussed on the list, it's a
myfaces-core issue and has to be fixed there -> no need to clone this issue.
> View with viewParameter remove backing-beans from the context in
> Restore-View-Phase when setting PROJECT_STAGE to Development
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: EXTCDI-222
> URL: https://issues.apache.org/jira/browse/EXTCDI-222
> Project: MyFaces CODI
> Issue Type: Bug
> Components: Core, JEE-JSF20-Module
> Environment: Tested on Jetty and IBM WebSphere 8
> Reporter: Steven Rudolf
>
> I use the ViewAccessScope from CODI.
> If I create a bean with viewAccessScope and link from a view (where the bean
> is called) to another view (where the bean is accessed too) and then go back
> to the original view, I expect, that the same instance of the bean is used.
> But at the time I go back to the original view in the Restore-View-Phase the
> instance of the bean is destroyed and a new one is created.
> This behaviour only happen if I use the PROJECT_STAGE=Development AND
> implement a viewParameter to the view. So I think, that in Development-Stage
> the <metadata>-Tag or the <viewParameter>-Tag do something that brings the
> BeanManager to handle the beans in abnormal way.
> There is a sample project at
> https://bitbucket.org/os890/myfaces-mailing-list/src/56d0ef922d12
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
