[
https://issues.apache.org/jira/browse/DELTASPIKE-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14159070#comment-14159070
]
Romain Manni-Bucau commented on DELTASPIKE-736:
-----------------------------------------------
[~struberg] I fixed it yesterday on OWB 1.5
BTW I agree the wrapper should be added *only* when needed and not everywhere
(can use apache-deltaspike.properties or a MockMatcher configurable in
apache-deltaspike.properties). This would also make the "skip" warnings
disappear which is quite nice on big apps where these logs are just too long to
keep logs useful.
wdyt?
> MockAwareInjectionTargetWrapper breaks interceptors in unit tests
> -----------------------------------------------------------------
>
> Key: DELTASPIKE-736
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-736
> Project: DeltaSpike
> Issue Type: Bug
> Components: TestControl
> Affects Versions: 1.0.3
> Environment: OpenWebBeans 1.2.6
> Reporter: Ronald Steininger
>
> The automatic usage of MockAwareInjectionTargetWrapper breaks method-level
> interceptors under OWB:
> org.apache.webbeans.config.BeansDeployer#validate creates the interceptor
> stack of all beans while validating the deployment (Line 474). This code
> depends on owbBean.getProducer() returning an AbstractProducer (Line 462).
> TestControl replaces that AbstractProducer in some circumstances with an
> instance of MockAwareInjectionTargetWrapper, completely deactivating the
> if-branch which would active the interceptors.
> It seems that, depending where the interceptor binding is defined on the
> intercepted bean, interceptors work or don't work: using the annotation on
> the class level results in getProducer returning a AbstractProducer ->
> interceptors work. Defining interceptors only on methods shows the broken
> behaviour described here.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
