[OWB-609] refactor conversation handling

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.1.1
• Fix Version/s: 1.6.0
• Component/s: Java EE Integration
• Assignee: Unassigned
• Reporter: Gerhard Petracek
• Created: 28/Aug/11 17:05
• Updated: 15/Jun/15 07:54
• Resolved: 15/May/15 07:55

Description

it's possible to use the bean-manager to resolve beans in a phase-listener, some portable cdi extensions (e.g. myfaces codi) allow to use dependency injection in phase-listeners and jsf 2.2+ might support it out-of-the-box.
so a conversation needs to be started before the lifecycle starts and the cleanup has to be done after all the rendering (and after all phase-listeners) because there are use-cases which access beans at the very beginning or even after a view was rendered (e.g. for cleanup tasks, logging,...) the current implementation in WebBeansPhaseListener leads to a constellation which isn't deterministic in case a conversation scoped bean gets accessed in the mentioned cases.

Issue Links

• relates to: OWB-626 Conversation Scope isn't accessible after RENDER_RESPONSE phase