[OWB-1095] Beans not fully initialized in AfterBeanDiscovery or InjectionPoint validation to early?

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.6.2
• Fix Version/s: 1.6.3
• Component/s: Core, Injection and Lookup
• Assignee: Thomas Andraschko
• Reporter: Thomas Andraschko
• Created: 16/Oct/15 13:37
• Updated: 11/Mar/16 21:58
• Resolved: 27/Oct/15 10:50

Description

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.