I've been fooling around with Interceptors and noticed some
unintuitive behavior when calling methods from a beans constructor
that should be intercepted.
For the first request, I see the shuffle method is intercepted.
Refreshing the JSP for a new RequestScoped instance of Foo causes no
interception at all!
@Named
@RequestScoped
public class Foo {
public Foo() {
...
shuffle();
}
@SomeInterceptorBinding
public void shuffle() {
}
}
If this is just undefined behavior, I think it's important to at least
make it internally consistent with respect what I guess is the re-use
of the proxy so we're either always/never intercepteed in this case.
Thoughts?
--
Eric Covener
[email protected]
