No Proxy for Dependent Scoped Bean when loaded from a JAR

[ora]

Hi,

I have a strange behaviour at the following scenario:

I'm running Weld 1.1.5.Final, JBoss AS 7.1.0.Final

Eclipse Project A contains:

• TestInterceptor : CDI-Interceptor
• DependentScopedBean : a dependent scoped bean with annotated usage of the TestInterceptor
• TestCase to inject a DependentScopeBean into an Arquillian TestCase and execute the interceptor on method invocation

-> TestCase works fine. DependenScopedBean is injected as a Proxy, Interceptor is executed

Eclipse Project B contains:

• dependency on Project A
• Same TestCase as in Project A

-> TestCase fails, because DependentScopedBean is injected as normal instance without proxy. Interceptor is not executed.

-> if I copy the DependentScopedBean in Project B and use it in the TestCase it works again

-> same if I don't run a TestCase with Arquillian (WebArchive) but a  call of a Web-Application.

Any help would be appreciated.

Thanks,

Oliver

[alesj]

Since you already have this as an Arquillian test,

can you somehow port it to our Weld Arquillian tests, and do a pull-request?

* https://github.com/weld/core/tree/master/tests-arquillian

[ora]

I don't think I can, at least I don't know how, because I need two projects to reproduce the problem.

I can only reproduce it, if I load the class of the dependentscoped bean from a jar.

If I include it in the same project (or to be more correct, package it as class not as lib in the arquillian-test) it works.

btw: on weld-se it works in all scenarios

[ora]

I think I've got the explanation. It seems I had a misunderstanding of activating interceptors.

I thought, I could activate the interceptor for the whole application (all archives in the war) in the beans.xml of the webarchive itself. But http://docs.jboss.org/weld/reference/1.1.0.Final/en-US/html_single/#d0e3556 states:

By default, all interceptors are disabled. We need to enable our interceptor in the beans.xml descriptor of a bean archive. This activation only applies to the beans in that archive.

So I've put the interceptor-activation to the Eclipse Project A and magic, now I've got a proxy and the interceptor is running in Project B.

One general point is not clear to me. If I want my Project A to be a shared library which is executed in an application X with interceptor and an application Y without an interceptor, how can I do this easily?

The approach to activate the interceptor in the WAR is obviously not working.

Another approach would be to work with another annotation instead of the interceptor-binding-annotation and link the two with an extension in application X. Is this the easies way to do this?