You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openwebbeans.apache.org by "Romain Manni-Bucau (JIRA)" <ji...@apache.org> on 2016/02/17 18:18:19 UTC

[jira] [Commented] (OWB-1119) Implement ConversationManagerService to plugin a custom manager

    [ https://issues.apache.org/jira/browse/OWB-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15150805#comment-15150805 ] 

Romain Manni-Bucau commented on OWB-1119:
-----------------------------------------

[~sessaid] hi, can you detail the use case you have we don't manage yet - we can maybe add it to OWB itself? If not an internal limitation you have access to all conversations so any listener (request one for instance) should be enough to work with the manager if needed, no?

> Implement ConversationManagerService to plugin a custom manager
> ---------------------------------------------------------------
>
>                 Key: OWB-1119
>                 URL: https://issues.apache.org/jira/browse/OWB-1119
>             Project: OpenWebBeans
>          Issue Type: Improvement
>          Components: Context and Scopes
>    Affects Versions: 1.6.2
>            Reporter: Shahim Essaid
>
> I'm working on a framework for using OpenWebBeans and it would be very helpful to be able to plugin my custom ConversationManager.  Currently the manager is simply  instantiated in WebBeansContext like this: 
>         conversationManager = new ConversationManager(this);
> Please implement the same logic for loading the ConversationManager as a service. I also didn't find an API way for overriding the instantiated ConversationManager with a new one after the WebBeansContext is instantiated. The initial services constructor parameter doesn't help with this either. I'm still new to the OpenWebBeans implementation and I don't think I know enough to be able to submit a patch to implement this.
> Did I miss how I can plugin my own manager with the current implementation?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)