Imagine the scenario where you have security implemented at the action
method level with an annotation:
@Secured("someRole") restricts that action to that role (and it is
checked with an interceptor).
Discussing this on the TDD mailing list a while back, a decorator
approach was suggested
To sep
Regarding this issue - and considering any interceptor, not just the
ExecAndWaitInterceptor:
1) My issue was, in fact, that I was accessing the request/session
scoped bean in my init method. The init method was being called at app
startup, where no such context exists
2) If we remove that access,
2 matches
Mail list logo
