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

Mark Struberg commented on OWB-1119:
------------------------------------

I rewrote the whole Conversation part only recently to better align it with the 
Servlet spec and Session handling.
The intention was to keep all the things pluggable (as most stuff in OWB). I 
hope I didn't trash anything during the rewrite though ;)
Our modularity scare some users at the first glance. But the benefit is that 
you can take the bare core (~500k) and pretty much plug and play very flexible 
depending on what you need.

The whole ConversationManager uses a 'ConversationStorageBean' which is 
basically a @SessionScoped bean. Thus it rather depends on how you handle the 
SessionContext. The rest is pretty agnostic. The ConversationStorageBean on the 
one side (storage) and the ConversationService to get the conversationId from 
where ever you like. http header, param, jsf view root, etc. Or even a 
ThreadLocal for you?

> 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)

Reply via email to