[
https://jira.jboss.org/jira/browse/RF-6831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Belaevski resolved RF-6831.
--------------------------------
Resolution: Rejected
The last view being saved wins, that's the right behavior.
> View replacement with an old one
> --------------------------------
>
> Key: RF-6831
> URL: https://jira.jboss.org/jira/browse/RF-6831
> Project: RichFaces
> Issue Type: Bug
> Affects Versions: 3.3.0
> Environment: Richfaces 3.3.0
> Reporter: Marjan Sterjev
>
> I'm running Richfaces 3.3.0 application configured with:
> <context-param>
> <param-name>com.sun.faces.numberOfViewsInSession</param-name>
> <param-value>0</param-value>
> </context-param>
>
> <context-param>
> <param-name>com.sun.faces.numberOfLogicalViews</param-name>
> <param-value>0</param-value>
> </context-param>
> i.e. only one view in the session at the moment.
> (This configuration is necessary because we are using <a4j:keepAlive> for
> persistence of the beans that generate the data tables. This way the links
> inside the data table will work).
> Consider the following scenario:
> 1. Make an Ajax request in the current view V1. Let us assume that it will
> run long enough.
> 2. Before the Ajax request is complete, navigate to another view V2 using
> normal browser submission. The next view V2 will be saved into the
> AjaxStateHolder.
> 3. In the mean time the long running Ajax request will finish and it will
> replace the current view V2 with the old one V1.
> 4. When we take some action in the browser, the view V2 is expired.
> Is this correct behavior? My opinion is that the Ajax request should not
> replace the current view if there is no more room for both.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
richfaces-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/richfaces-issues
