No way to exclude @RequestScope beans from being excluded #7
Description
The bean filtering mechanism assumes that every bean would be accessible by name from the ApplicationContext before it's handed to the BeanMatcher. This breaks for @RequestScope beans as that access is trying to create an actual instance of the bean and will fail in a simple test execution.
It would be cool if it was possible to filter which beans to include based on the sole BeanDefinition, too. This would also avoid the need to even instantiate the beans that are not supposed to be included in the diagram to be created.