APPLICATION FAILED TO START ”A component required a bean named '***' that could not be found.“

[prefect1005]

Bug Report

Which version of ElasticJob did you use?

elasticjob-lite-spring-boot-starter 3.0.1

Which project did you use? ElasticJob-Lite or ElasticJob-Cloud?

ElasticJob-Lite

Actual behavior

---

APPLICATION FAILED TO START

---

Description:
A component required a bean named 'myOneOffJobBean' that could not be found.

my config:
elasticjob.jobs.oneOffJob.elasticJobClass=com.example.demo.MyElasticJob
elasticjob.jobs.oneOffJob.jobBootstrapBeanName=myOneOffJobBean
elasticjob.jobs.oneOffJob.shardingTotalCount=3

in controller:
@resource(name = "myOneOffJobBean")
private OneOffJobBootstrap myOneOffJobBean;

Reason analyze (If you can)

in 3.0.0 version is ok
i find
#1810
this issues

and in this merge
0446a5d
JobBootstrapBeans instantiation in afterSingletonsInstantiated

just because of this，in application Controller ， the OneOffJobBootstrap has not init.
so what can i do?

hope to reply, thanks

Steps to reproduce the behavior.

Example codes for reproduce this issue (such as a github link).

[DoolinMa]

@prefect1005 you can put @lazy annotation on Controller to make sure the application is running normally

@Lazy
public class OneOffJobController {

[cocodroid]

You can also use @Autowried(required=false) @qualifier("myOneOffJobBean")

[ceylog]

I also have the same problem

[kingkh1995]

#1930 this fix is the cause of this issue, i think the only solution is lazy init, but OneOffBootStrap is final.

#1810 if we need to autowire OneOffBootStrap, OneOffBootStrap need to be registered before AutowiredAnnotationBeanPostProcessor, so ElasticJobProperties bean need to be initialized before AutowiredAnnotationBeanPostProcessor, which means ElasticJobProperties will be not eligible for getting processed by all BeanPostProcessors.

[linghengqian]

#1930 this fix is the cause of this issue, i think the only solution is to lazy init, but OneOffBootStrap is final.

• I'm tracking this behavior at Provide built-in GraalVM Reachability Metadata and introduce a separate nativeTest in CI #2258 . There are known issues with the Spring Bean introspection of ElasticJob Lite's Spring Boot Starter, and similar behavior has been found in many third-party Spring Boot Starters.

[kingkh1995]

another way is to use @lookup, is this okay? @linghengqian

@Lookup("onceJobBootstrap")
public OneOffJobBootstrap getOnceJobBootstrap() {
    return null;
}

[linghengqian]

• @prefect1005 I'm no Spring expert, but the reality is that some beans in ElasticJob's Spring Boot Starter may require additional fully parameterized constructors.

• There is no movement in Provide built-in GraalVM Reachability Metadata and introduce a separate nativeTest in CI #2258 mainly because I am working on Improve GraalVM Reachability Metadata and corresponding nativeTest related unit tests shardingsphere#29052 and can’t spare much time.

[linghengqian]

• Reproduced at Provides built-in GraalVM Reachability Metadata and nativeTest on Elasticjob Spring Boot Starter under Spring Boot 3.3.2 #2417 . I will fix this documentation issue.
• I personally would never recommend using @Lazy, it is not in line with normal human thinking.