[
https://issues.apache.org/jira/browse/OWB-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14960743#comment-14960743
]
Gerhard Petracek commented on OWB-1095:
---------------------------------------
the issue is in InjectionResolver.
it contains an empty value in resolvedComponents for the key in question.
we just need to change
{code}
Set<Bean<?>> resolvedComponents = resolvedBeansByType.get(cacheKey);
if (resolvedComponents != null)
{
return resolvedComponents;
}
{code}
to
{code}
Set<Bean<?>> resolvedComponents = resolvedBeansByType.get(cacheKey);
if (resolvedComponents != null && !resolvedComponents.isEmpty())
{
return resolvedComponents;
}
{code}
and it will work.
> 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)
