You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openwebbeans.apache.org by "Thomas Andraschko (JIRA)" <ji...@apache.org> on 2015/10/16 15:40:05 UTC
[jira] [Commented] (OWB-1095) Beans not fully initialized in
AfterBeanDiscovery or InjectionPoint validation to early?
[ https://issues.apache.org/jira/browse/OWB-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14960706#comment-14960706 ]
Thomas Andraschko commented on OWB-1095:
----------------------------------------
[~struberg] [~romain.manni-bucau] Could anyone of you please take at look at it?
> 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
> Fix For: 1.6.3
>
> Attachments: owb-ds-test.7z
>
>
> DeltaSpike's ConverterAndValidatorProxyExtension possible adds new beans via afterBeanDiscovery#addBean 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 "not 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)