bq. I missed the `decorate` call in the deploy()-method, ...
Yea this is a programmatic (test-only) way to enable them as if you had {{beans.xml}}. If you just used {{@Priority}}, it should work even without it.
bq. However, I am still struggling with a decorator which only started working after I moved default impls to the abstract class
So you still have the problem? Could you try tackling the reproducer so that it shows the issue?
bq. You wouldn't happen to have any pointers...
You mean debugging proxy/subclass creation? Interception/decoration itself is (roughly speaking) "just" invoking a method on the generated proxy then.
You can dump created proxy classes using [this option|http://docs.jboss.org/weld/reference/latest-master/en-US/html_single/#_debugging_generated_bytecode].
Other than that, most proxy creation (_for decorators_) is done in [ProxyFactory|https://github.com/weld/core/blob/master/impl/src/main/java/org/jboss/weld/bean/proxy/ProxyFactory.java] and [DecoratorProxyFactory|https://github.com/weld/core/blob/master/impl/src/main/java/org/jboss/weld/bean/proxy/DecoratorProxyFactory.java].
But it's pretty complex and I would rather suggest you put together the reproducer and we can go from there. |
|
