[jira] [Updated] (OWB-1074) implement automatic supportsConversation() detection
[ https://issues.apache.org/jira/browse/OWB-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau updated OWB-1074: Fix Version/s: 2.0.27 (was: 2.0.26) > 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 >Priority: Major > Fix For: 2.0.27 > > > 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 (v8.20.1#820001)
[jira] [Updated] (OWB-1074) implement automatic supportsConversation() detection
[ https://issues.apache.org/jira/browse/OWB-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated OWB-1074: --- Fix Version/s: 2.0.26 (was: 2.0.25) > 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 >Priority: Major > Fix For: 2.0.26 > > > 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 (v8.20.1#820001)
[jira] [Updated] (OWB-1074) implement automatic supportsConversation() detection
[ https://issues.apache.org/jira/browse/OWB-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Louis Monteiro updated OWB-1074: - Fix Version/s: 2.0.25 (was: 2.0.24) > 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 >Priority: Major > Fix For: 2.0.25 > > > 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 (v8.20.1#820001)
[jira] [Updated] (OWB-1074) implement automatic supportsConversation() detection
[ https://issues.apache.org/jira/browse/OWB-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau updated OWB-1074: Fix Version/s: (was: 2.0.23) 2.0.24 > 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 >Priority: Major > Fix For: 2.0.24 > > > 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 (v8.3.4#803005)
[jira] [Updated] (OWB-1074) implement automatic supportsConversation() detection
[ https://issues.apache.org/jira/browse/OWB-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated OWB-1074: --- Fix Version/s: (was: 2.0.22) 2.0.23 > 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 >Priority: Major > Fix For: 2.0.23 > > > 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 (v8.3.4#803005)
[jira] [Updated] (OWB-1074) implement automatic supportsConversation() detection
[ https://issues.apache.org/jira/browse/OWB-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau updated OWB-1074: Fix Version/s: (was: 2.0.21) 2.0.22 > 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 >Priority: Major > Fix For: 2.0.22 > > > 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 (v8.3.4#803005)
[jira] [Updated] (OWB-1074) implement automatic supportsConversation() detection
[ https://issues.apache.org/jira/browse/OWB-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau updated OWB-1074: Fix Version/s: (was: 2.0.20) 2.0.21 > 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 >Priority: Major > Fix For: 2.0.21 > > > 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 (v8.3.4#803005)
[jira] [Updated] (OWB-1074) implement automatic supportsConversation() detection
[ https://issues.apache.org/jira/browse/OWB-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau updated OWB-1074: Fix Version/s: (was: 2.0.16) 2.0.17 > 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 >Priority: Major > Fix For: 2.0.17 > > > 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 (v8.3.4#803005)
[jira] [Updated] (OWB-1074) implement automatic supportsConversation() detection
[ https://issues.apache.org/jira/browse/OWB-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau updated OWB-1074: Fix Version/s: (was: 2.0.15) 2.0.16 > 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 >Priority: Major > Fix For: 2.0.16 > > > 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 (v8.3.4#803005)
[jira] [Updated] (OWB-1074) implement automatic supportsConversation() detection
[ https://issues.apache.org/jira/browse/OWB-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau updated OWB-1074: Fix Version/s: (was: 2.0.13) 2.0.14 > 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 >Priority: Major > Fix For: 2.0.14 > > > 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 (v8.3.4#803005)
[jira] [Updated] (OWB-1074) implement automatic supportsConversation() detection
[ https://issues.apache.org/jira/browse/OWB-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau updated OWB-1074: Fix Version/s: (was: 2.0.12) 2.0.13 > 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 >Priority: Major > Fix For: 2.0.13 > > > 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 (v8.3.4#803005)
[jira] [Updated] (OWB-1074) implement automatic supportsConversation() detection
[ https://issues.apache.org/jira/browse/OWB-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau updated OWB-1074: Fix Version/s: (was: 2.0.11) 2.0.12 > 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 >Priority: Major > Fix For: 2.0.12 > > > 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 (v7.6.3#76005)
[jira] [Updated] (OWB-1074) implement automatic supportsConversation() detection
[ https://issues.apache.org/jira/browse/OWB-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau updated OWB-1074: Fix Version/s: (was: 2.0.10) 2.0.11 > 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 >Priority: Major > Fix For: 2.0.11 > > > 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 (v7.6.3#76005)
[jira] [Updated] (OWB-1074) implement automatic supportsConversation() detection
[ https://issues.apache.org/jira/browse/OWB-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau updated OWB-1074: Fix Version/s: (was: 2.0.9) 2.0.10 > 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 >Priority: Major > Fix For: 2.0.10 > > > 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 (v7.6.3#76005)
[jira] [Updated] (OWB-1074) implement automatic supportsConversation() detection
[ https://issues.apache.org/jira/browse/OWB-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Andraschko updated OWB-1074: --- Fix Version/s: (was: 2.0.8) 2.0.9 > 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 >Priority: Major > Fix For: 2.0.9 > > > 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 (v7.6.3#76005)
[jira] [Updated] (OWB-1074) implement automatic supportsConversation() detection
[ https://issues.apache.org/jira/browse/OWB-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated OWB-1074: --- Fix Version/s: (was: 2.0.6) 2.0.7 > 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 >Priority: Major > Fix For: 2.0.7 > > > 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 (v7.6.3#76005)
[jira] [Updated] (OWB-1074) implement automatic supportsConversation() detection
[ https://issues.apache.org/jira/browse/OWB-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated OWB-1074: --- Fix Version/s: (was: 2.0.5) 2.0.6 > 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 >Priority: Major > Fix For: 2.0.6 > > > 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 (v7.6.3#76005)
[jira] [Updated] (OWB-1074) implement automatic supportsConversation() detection
[ https://issues.apache.org/jira/browse/OWB-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated OWB-1074: --- Fix Version/s: (was: 2.0.4) 2.0.5 > 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 >Priority: Major > Fix For: 2.0.5 > > > 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 (v7.6.3#76005)
[jira] [Updated] (OWB-1074) implement automatic supportsConversation() detection
[ https://issues.apache.org/jira/browse/OWB-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated OWB-1074: --- Fix Version/s: (was: 2.0.3) 2.0.4 > 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: 2.0.4 > > > 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.4.14#64029)
[jira] [Updated] (OWB-1074) implement automatic supportsConversation() detection
[ https://issues.apache.org/jira/browse/OWB-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated OWB-1074: --- Fix Version/s: (was: 1.7.5) 2.0.3 > 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: 2.0.3 > > > 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.4.14#64029)
[jira] [Updated] (OWB-1074) implement automatic supportsConversation() detection
[ https://issues.apache.org/jira/browse/OWB-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated OWB-1074: --- Fix Version/s: (was: 1.7.4) > 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.7.5 > > > 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.4.14#64029)
[jira] [Updated] (OWB-1074) implement automatic supportsConversation() detection
[ https://issues.apache.org/jira/browse/OWB-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated OWB-1074: --- Fix Version/s: (was: 1.7.2) 1.7.3 > 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.7.3 > > > 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.15#6346)
[jira] [Updated] (OWB-1074) implement automatic supportsConversation() detection
[ https://issues.apache.org/jira/browse/OWB-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated OWB-1074: --- Fix Version/s: (was: 1.6.3) 1.6.4 > 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.4 > > > 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)
[jira] [Updated] (OWB-1074) implement automatic supportsConversation() detection
[ https://issues.apache.org/jira/browse/OWB-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated OWB-1074: --- Fix Version/s: (was: 1.6.2) 1.6.3 > 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.3 > > > 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)
[jira] [Updated] (OWB-1074) implement automatic supportsConversation() detection
[ https://issues.apache.org/jira/browse/OWB-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated OWB-1074: --- Fix Version/s: (was: 1.6.1) 1.6.2 > 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.2 > > > 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)
[jira] [Updated] (OWB-1074) implement automatic supportsConversation() detection
[ https://issues.apache.org/jira/browse/OWB-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated OWB-1074: --- Fix Version/s: (was: 1.6.0) 1.6.1 > 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.1 > > > 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)