postProcessBeanFactory() already throws BeansException, it seems that you need to clear the try-catch or clear the throws.
Comment From: pivotal-cla
@cyeji Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.
Comment From: wilkinsona
Thanks for the proposal but the try-catch is intentional here. It means that the for-loop will continue should a failure occur within the loop.
Comment From: cyeji
@wilkinsona Thank you for your answer. I have a question. Then already caught all the errors in the iteration, but is there a reason to throw them in the method? I think already caught an error, but I'm wondering why you're throwing an error toward the caller.
Comment From: wilkinsona
We're catching and swallowing NoSuchBeanDefinitionException as we want them to be ignored and for processing to continue. Any other BeansException should abort processing and reach the caller.