[jira] Commented: (EXTCDI-49) @ViewAccessScoped in combination with h:link and back-buttons

["Gerhard Petracek (JIRA)" <de...@myfaces.apache.org>]

    [ https://issues.apache.org/jira/browse/EXTCDI-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12932070#action_12932070 ] 

Gerhard Petracek commented on EXTCDI-49:
----------------------------------------

we should introduce an optional (2nd) mechanism which checks all access-view-scoped beans after the rendering process.

> @ViewAccessScoped in combination with h:link and back-buttons
> -------------------------------------------------------------
>
>                 Key: EXTCDI-49
>                 URL: https://issues.apache.org/jira/browse/EXTCDI-49
>             Project: MyFaces CODI
>          Issue Type: Bug
>          Components: JEE-JSF20-Module
>            Reporter: Mark Struberg
>            Priority: Minor
>
> I added the following small listsample extension to our JSF-2 sample to demonstrate the problem
> 1.) a sampleList.xhtml which shows 3 entries in a h:dataTable using a SampleList.java bean
> 2.) a sampleListEntry.xhtml which shows the id given as f:viewParam to the SampleListEntry bean along with a free String value
> Both beans log a INFO message in a @PostConstruct method if they get initialised.
> To reproduce the bug:
> * Select the entry "1" and enter "ping" into the "value" field
> * Click the "back" button
> * Now select the entry "2". You will still see the 'old' value "ping" in the "value" field and if you look at the log, then it will miss the INFO message for creating the ViewAccessScoped bean.
> Imo a new instance of the SampleListEntry bean should get created each time I freshly re-enter the sampleListEntry.xhtml page again (since it doesn't get touched on the sampleList.xhtml list page!)

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