You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@deltaspike.apache.org by "Ortwin Escher (JIRA)" <ji...@apache.org> on 2014/12/08 10:05:12 UTC
[jira] [Updated] (DELTASPIKE-795) ViewAccessScope gets destroyed in
combination with f:viewAction
[ https://issues.apache.org/jira/browse/DELTASPIKE-795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ortwin Escher updated DELTASPIKE-795:
-------------------------------------
Attachment: DemoDeltaspikeScope.zip
Attached a demo application for Wildfly 8.2/DeltaSpike 1.2.0. In comparison to the one posted on the user mailing list it has a ds:windowId on every page and a head and body element as requested.
> ViewAccessScope gets destroyed in combination with f:viewAction
> ---------------------------------------------------------------
>
> Key: DELTASPIKE-795
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-795
> Project: DeltaSpike
> Issue Type: Bug
> Components: JSF-Module
> Affects Versions: 1.2.0
> Reporter: Ortwin Escher
> Attachments: DemoDeltaspikeScope.zip
>
>
> Initial setup:
> Two ViewAccessScoped beans, two pages and both beans are accessed on both pages.
> Expected behavior:
> When navigating between the two pages both ViewAccessScope should stay alive regardless of f:viewActions.
> Actual behavior:
> The f:viewAction seems to count as an additional request for DeltaSpike and thus destroys all ViewAccessScoped beans that are not touched by it. Accessing one of the ViewAccessScoped beans in a f:viewAction destroys the bean that is not accessed. Accessing none of the ViewAccessScoped beans will destroy all ViewAccessScoped beans.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)