[
https://issues.apache.org/jira/browse/OWB-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14960754#comment-14960754
]
Gerhard Petracek edited comment on OWB-1095 at 10/16/15 2:04 PM:
-----------------------------------------------------------------
no - the empty value is stored too early in that case, because at some point
there would be a value.
(just debug it with the provided example and set the result to null to run the
code after the if-statement and it will work.)
@don't cache before the startup finished:
+1
that would be my suggestion as well (at least in case of empty values - if we
need to keep them)
was (Author: gpetracek):
no - the empty value is stored too early in that case, because at some point
there would be a value.
(just debug it with the provided example and set the result to null to run the
code after the if-statement 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)
