Exclude infrastructure beans from lazy init early

[hojooo]

ROLE_INFRASTRUCTURE bean added early return logic prior to bean type interpretation(getType) to be excluded from lazy-init in any case.
I think this code can eliminate the possibility that Infrastructure bean will accidentally turn into Lazy-init=true, even if beanType is null or type inference is limited.

[snicoll]

@hojooo thanks for the PR but we can't make this change without an actionable issue. Please provide that and then we can see if we want to make this change.

[hojooo]

@snicoll Thanks for the feedback!

I think getBeanType() can return null in the following situation.

@Component  
@Role(BeanDefinition.ROLE_INFRASTRUCTURE)
public class InfrastructureBean implements FactoryBean<Object> {
    
    @Override
    public Object getObject() {
        return new SomeInfrastructureComponent();
    }
    
    @Override
    public Class<?> getObjectType() {
        return null;  // FactoryBean allows null
    }
}

Spring's own FactoryBean contract allows null, and this change ensures infrastructure beans remain protected even in these edge cases. Is this too unusual? I thought it was better to exclude it more explicitly. Thank you!

[snicoll]

Thanks for following up.

Spring's own FactoryBean contract allows null,

Yes, I am aware of that. and isExcluded that is called here does account for the fact that beanType may be null. If that's what you were trying to protect against, then the code as we have is fine.