[
https://issues.apache.org/jira/browse/OWB-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14961002#comment-14961002
]
Romain Manni-Bucau commented on OWB-1095:
-----------------------------------------
[~struberg] we clear it between events (not all but you get the idea), here we
need to clear it between extensions for the same event. With few extension
doing this kind of things it is ok but thinking to monitoring extension
wrapping a bunch of beans it is an open question. That said if impacting and
for this event only in term of scope we can cache the reflection result
(isAssignable logic)
> 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)
