[
https://issues.apache.org/jira/browse/OWB-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14960747#comment-14960747
]
Romain Manni-Bucau commented on OWB-1095:
-----------------------------------------
[~gpetracek] empty is a valid cached value we have to trust in
InjectionResolver IMO, the issue can be we need to de-cache between all
extensions of AfterBeanDiscovery or not cache at all before the end of the
startup (but it can have some serious perf impacts).
> Beans not fully initialized in AfterBeanDiscovery or InjectionPoint
> validation to early?
> ----------------------------------------------------------------------------------------
>
> Key: OWB-1095
> URL: https://issues.apache.org/jira/browse/OWB-1095
> Project: OpenWebBeans
> Issue Type: Bug
> Components: Core, Injection and Lookup
> Affects Versions: 1.6.2
> Reporter: Thomas Andraschko
> Priority: Critical
> Fix For: 1.6.3
>
> Attachments: owb-ds-test.7z
>
>
> DeltaSpike's ConverterAndValidatorProxyExtension possible adds new beans via
> afterBeanDiscovery#addBean and DS BeanBuilder if the JSF converter needs to
> be proxied.
> However, when the converter has a injectionPoint, it will be created during
> AfterBeanDiscovery via beanManager#createInjectionTarget but OWB always
> throws "no bean available for class ..."
> This works fine in older OWB versions and other containers.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
