Details
Bug
Major
Description
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.
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
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