[
https://issues.apache.org/jira/browse/OWB-609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved OWB-609.
-------------------------------
Resolution: Fixed
Fix Version/s: (was: 1.5.1)
1.6.0
With the latest Conversation rework the behaviour is now consistent at least. I
agree we could do even more but the spec doesn't require this. And native CDI
Conversations are rarely used anyway, so not sure if it's worth.
> refactor conversation handling
> ------------------------------
>
> Key: OWB-609
> URL: https://issues.apache.org/jira/browse/OWB-609
> Project: OpenWebBeans
> Issue Type: Improvement
> Components: Java EE Integration
> Affects Versions: 1.1.1
> Reporter: Gerhard Petracek
> Priority: Minor
> Fix For: 1.6.0
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
