How to bypass response filter when response is from exception mapper


How to bypass response filter when response is from exception mapper



Is there a way to bypass response filter execution in exception case?



Say I have an exception mapper to create a response for certain exception and I don't want response filter executed for this case.



I only want my response filter executed for normal 200 case.



I saw ContainerResponse has some property to indicate it's from exception.
But that requires each response filter to do the check accordingly.



Is there any way else like using some annotation or config to mark this response filter only for 200?



Thanks



Leon





No, it's just how it's designed.
– Paul Samsotha
Jun 30 at 4:42





OK, Thanks a lot!
– anuni
9 hours ago









By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Comments

Popular posts from this blog

paramiko-expect timeout is happening after executing the command

how to run turtle graphics in Colaboratory

Export result set on Dbeaver to CSV