官术网_书友最值得收藏!

How it works...

If we run our application again, by executing $ ./gradlew clean bootRun, we will get an output that is similar to the previous one. However, we will see our Hello message in the logs as well, which is as follows:

2017-12-16 21:57:51.048  INFO --- 
com.example.bookpub.StartupRunner : Hello

Even though the program will get terminated on execution, at least we made it do something!

Command-line runners are a useful functionality to execute the various types of code that only have to be run once, after startup. Some also use this as a place to start various executor threads, but Spring Boot provides a better solution for this task, which will be discussed at the end of this chapter. The command-line runner interface is used by Spring Boot to scan all of its implementations and invoke each instance's run method with the startup arguments. We can also use an @Order annotation or implement an Ordered interface so as to define the exact order in which we want Spring Boot to execute them. For example, Spring Batch relies on the runners to trigger the execution of the jobs.

As the command-line runners are instantiated and executed after the application has started, we can use the dependency injection to our advantage to wire in whatever dependencies we need, such as datasources, services, and other components. These can be utilized later while implementing run.

It is important to note that if any exception is thrown in the run(String... args) method, this will cause the context to close and an application to shut down. Wrapping the risky code blocks with try/catch is recommended to prevent this from happening.
主站蜘蛛池模板: 徐水县| 游戏| 桃园市| 策勒县| 辰溪县| 安阳县| 麦盖提县| 资阳市| 柯坪县| 蒙城县| 海口市| 岫岩| 林西县| 武邑县| 大洼县| 古田县| 沾化县| 青岛市| 安陆市| 靖西县| 宾川县| 西青区| 靖州| 玉溪市| 新平| 巩留县| 西昌市| 北碚区| 巨鹿县| 收藏| 航空| 巨野县| 武安市| 平昌县| 开化县| 同心县| 兴山县| 竹北市| 永胜县| 杭州市| 武定县|