[
https://issues.apache.org/jira/browse/OWB-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14545173#comment-14545173
]
Romain Manni-Bucau commented on OWB-1074:
-----------------------------------------
I think when we'll tackle it we should remove the supportsConversation property
since iterating over beans to check their scope should be fast enough. Then
auto mode would be the only needed one.
> implement automatic supportsConversation() detection
> ----------------------------------------------------
>
> Key: OWB-1074
> URL: https://issues.apache.org/jira/browse/OWB-1074
> Project: OpenWebBeans
> Issue Type: Improvement
> Components: Context and Scopes
> Affects Versions: 1.5.0
> Reporter: Mark Struberg
> Fix For: 1.6.0
>
>
> Currently we rely on the user to define the configuration option in
> OpenWebBeansConfiguration
> {code}
> APPLICATION_SUPPORTS_CONVERSATION =
> "org.apache.webbeans.application.supportsConversation";
> {code}
> This is by default disabled in owb-impl (core) and gets enabled by adding the
> web or jsf plugins.
> We could improve this by not only allowing {{true}} or {{false}} but also
> with an {{auto}} mode.
> In this mode the BeanManager can walk through all registered beans and check
> whether there is a single @ConversationScoped bean. In that case we will
> automagically enable CDI conversations, otherwise OWB will dynamically
> disable conversation support and don't need to do all kinds of work in
> WebContextsService for example.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
