> Out of curiosity do we know which resolver is configured that is potentially > causing the problem? We should fix that to be compliant with the API that > says don't throw exceptions :-)
The problem is that the NPE is masking the resolver error. What's more concerning is that resolver failures, which can happen in ways other than throwing exceptions (e.g. returning null), can mask thrown exceptions that arise from evaluation of the join point. In that case Inspketr is quite intrusive to the application. That said I'm not entirely certain my patch will help because I'm just guessing Brian has run into the same issues as I have in the past. I'm hopeful the patch will provide the logging needed to indicate the problem CAS component. In that case we'll also have a patch that demonstrates improved auditing behavior (at least in this one case), which is a lot more than I had when I opened https://github.com/dima767/inspektr/issues/10 ages ago. M -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
