[
https://issues.apache.org/jira/browse/OWB-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14960726#comment-14960726
]
Romain Manni-Bucau commented on OWB-1095:
-----------------------------------------
org.apache.deltaspike.proxy.api.DeltaSpikeProxyContextualLifecycle#DeltaSpikeProxyContextualLifecycle
create an injection target before
org.apache.deltaspike.core.impl.scope.DeltaSpikeContextExtension#registerDeltaSpikeContexts
is called so validation of the injection target fails
ordering both extensions in DS should work
regarding the spec this createInjectiontarget has been deprecated for
InjectionTargetFactory instead, maybe introducing this cdi 1.1 API in DS (like
CDI.current() has been introduced) can solve this issue?
> 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)
