-
Clarification
-
Resolution: Done
-
Major
-
1.0
-
None
When implementing interception using proxying the behaour of self invocation is quite well defined, if a method is invoked on the proxy it is intercepted, if it is invoked on the actual bean (usually through self-invocation) it is not.
When implementing interception though sub classing this is much less well definied, and the only way to track if an invocation is intercepted or not is through a thread local flag. At the moment in weld this is reset when a call is made on a client proxy, so if we have an intercepted bean A and a SessionScoped bean B and A invokes B when invokes A the second call to A is intercepted. If however B is pseudo scoped, then the second invocation is not intercepted. The correct behaviour here should be specified by the specification.
- blocks
-
CDITCK-311 Align the tests for unproxyable bean types with the current wording of the spec
- Resolved
- is related to
-
CDI-10 Add ability to access a bean instance from a proxy
- Closed
-
CDI-74 State explicitely that Decorators must be implemented using subclassing
- Closed
- relates to
-
WELD-1227 Implement unproxyable type checks for decorated/intercepted beans
- Resolved