Details
Bug
Major
Description
In version 1.8, using the same configuration, request-scoped beans are now disposed and new instances created. The one caveat is that if DisposableBean is implemented, the dispose() method is not called.
We need to decide between:
1) Reverting the behaviour to work like 1.7
2) Leave the existing behaviour but fix the dispose() call
3) Allow both behaviours through some kind of configuration
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
What about with backward-compatibility?
I got some apps created and optimized for icefaces 1.7.*, concurrentDOMViews and standardRequestScope are both set to false too.
In year 2008 everything works well but now on 1.8.1 i got performance issues. Request beans and all associated data are recreated and reloaded very often.
My navigations are based on menu actions and "navigation-case" with "redirect" (support for "back" button and history).
I don't wan't change beans scope to session and remove "redirect". Is any solution?
Behaviour from RequestBeanChart.TIF doesn't work for Icefaces 1.8.1 -case concurrentDOMViews and standardRequestScope are both set to false
Above issues are visible on 1.8.1 revison 19141 from trunk.
Krashan, please create a new JIRA for this as this one cannot be re-opened since it has already shipped with associated changes in 1.8.1. Also, you need to attach a simple test application to demonstrate the issue you are reporting to the new JIRA.
Hi!
I'm using iceFaces 1.8.2 and I still face the problem as "In version 1.7, when concurrentDOMViews and standardRequestScope are both set to false, a page reload would NOT cause the current request-scoped beans to be disposed and new instances of request-scoped beans to be created. Basically, request-scoped beans would hang around between reloads. "
I've restored the behavior to what it was in 1.7.2. The noticeable problem was that all request scoped objects were going out of scope on reload, but the dispose() method was not being called on any request scoped beans implementing the DisposableBean interface. This was due to a new ExternalContext always being created on reload. This has been restored in svn version: 18861.
The current behaviour matrix is attached. There seems to be an anomaly with concurrentDOMViews = true and standardRequestScope = false. It might be argued that the request scoped beans should stick around in the case of reload. Digging into this, I found that on reload an $
{app}/block/disposeViews request is sent to the server first, prior to the client re-requesting the page and with concurrentDOMViews set to true, a disposeViews request actually disposes the Views as opposed to only reusing them in the concurrentDOMViews=false case. As part of this disposing the views, the externalContext is disposed. When the View is disposed, all its member variables of course are gone too. This means it would be tricky to keep the externalContext around with the request Map containing the beans. I suggest leaving the behaviour just as it is.