[ 
https://issues.apache.org/jira/browse/DELTASPIKE-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14159127#comment-14159127
 ] 

Gerhard Petracek commented on DELTASPIKE-736:
---------------------------------------------

we should check which versions are really affected (besides owb 1.2) and 
continue the discussion afterwards.
we just need to ensure that it works for the majority of versions, otherwise we 
would need to drop most features just because some old servers are broken.
we agreed against that already - so let's see which versions are affected in 
detail.

> 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
>         Attachments: ds-736-demo.tgz
>
>
> 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)

Reply via email to