[jira] [Commented] (OWB-1120) Expose singleContextMap and contextMap from BeanManagerImpl as API

["Romain Manni-Bucau (JIRA)" <ji...@apache.org>]

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

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

You can already control context though ContextsService so any further internals access can be broken in any minor version. I don't see any reason to do so to be honest and it seems your context handling is all but CDI since all you enumerated can already be done IMO with custom contexts and contexts - custom or not - can already be controlled with deltaspike-ctrl for instance or OWB ContextsService. What do you try to achieve you can't do today using 100% CDI API? Any code sample would maybe make it clearer.

> Expose singleContextMap and contextMap from BeanManagerImpl as API
> ------------------------------------------------------------------
>
>                 Key: OWB-1120
>                 URL: https://issues.apache.org/jira/browse/OWB-1120
>             Project: OpenWebBeans
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 1.6.2
>            Reporter: Shahim Essaid
>
> My custom ContextsService needs to lookup contexts from the singleContextMap and contextMap from BeanManagerImpl. The current implementation doesn't allow this and it fully controls the order of context lookup:
> 1. Check the service.
> 2. Check singleContextMap
> 3. Check contextMap.
> In my custom service I'm implementing a default context resolution strategy (that implements flat or nested contexts) and it can be configured to do the following:
> 1. Always use the built-in context resolution strategy.
> 2. Look in the CDI container for any provided strategies, and then use built-in if needed
> 3. Check for any Extension provided contexts and decide to override with container provided or built-in strategy.
> 4. etc.
> The BeanManagerImpl doesn't expose the custom context maps
> on their own to help with this. I can use reflection or make another call to getContext() and return null from my service to find other contexts but a well defined API might be useful; at least to be able to get copies of those maps.



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