You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openwebbeans.apache.org by "Mark Struberg (JIRA)" <ji...@apache.org> on 2019/07/11 13:36:00 UTC
[jira] [Resolved] (OWB-1294) disable implicitInjectionPoint by
default
[ https://issues.apache.org/jira/browse/OWB-1294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Struberg resolved OWB-1294.
--------------------------------
Resolution: Fixed
the default mode is now off.
It can be enabled by adding the following setting to {{META-INF/openwebbeans/openwebbeans.properties}}:
{noformat}
org.apache.webbeans.service.DefaultInjectionPointService..implicitSupport=true
{noformat}
> disable implicitInjectionPoint by default
> -----------------------------------------
>
> Key: OWB-1294
> URL: https://issues.apache.org/jira/browse/OWB-1294
> Project: OpenWebBeans
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.0.11
> Reporter: Mark Struberg
> Assignee: Mark Struberg
> Priority: Major
> Fix For: 2.0.12
>
>
> OWB-1287 introduced a way to make the {{@Inject}} annotation optional if a Qualifier exists. But we have run into problems with this setting. It also introduces a slight performance degrading so we'd rather should make this an optional feature.
> The problematic case is whenever another framework (in our case Mockito and in Maven modules) handles a field and also uses a JSR-330 Qualifier for it. With the implicitInjectionPoint feature the CDI container will overwrite mock objects.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)