Jan 16th, 2013, 01:55 PM
Sorry it took so long for me to articulate the issue!
Originally Posted by Gary Russell
Hmm, so in terms of exception logging the chain ID solution is the best that can be currently done it seems. It's helpful, but doesn't seem ideal to me. Though it might be very low priority, is there any hope for enhancing the exception message?
Would it be appropriate for the filter bean to throw its own exception rather than relying on the throw-exception-on-rejection attribute?
On second thought, I guess the current message is probably fine.