Skip to content

Commit 1d7b486

Browse files
committed
Updated docs
1 parent 78f27ef commit 1d7b486

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

docs/src/main/asciidoc/stream.adoc

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ NOTE: If the payload is of a different type, the sink throws an exception.
2929
For example, a stream can be created that has a processor that takes in data from an
3030
HTTP source and creates a `GenericMessage` that contains the `TaskLaunchRequest` and sends
3131
the message to its output channel. The task sink would then receive the message from its
32-
input channnel and then launch the task.
32+
input channel and then launch the task.
3333

3434
To create a taskSink, you need only create a Spring Boot application that includes the
3535
`EnableTaskLauncher` annotation, as shown in the following example:
@@ -103,11 +103,11 @@ public class TaskEventsApplication {
103103
public static class TaskConfiguration {
104104
105105
@Bean
106-
public CommandLineRunner commandLineRunner() {
107-
return new CommandLineRunner() {
106+
public ApplicationRunner applicationRunner() {
107+
return new ApplicationRunner() {
108108
@Override
109-
public void run(String... args) throws Exception {
110-
System.out.println("The CommandLineRunner was executed");
109+
public void run(ApplicationArguments args) {
110+
System.out.println("The ApplicationRunner was executed");
111111
}
112112
};
113113
}
@@ -172,7 +172,7 @@ if `StepExecutionListener` needs to emit its messages to another channel called
172172
`my-step-execution-events` instead of the default `step-execution-events`, you can add the
173173
following configuration:
174174

175-
`spring.cloud.stream.bindings.step-execution-events.destination=my-step-execution-events`
175+
`spring.cloud.task.batch.events.step-execution-events-binding-name=my-step-execution-events`
176176

177177
=== Disabling Batch Events
178178
To disable the listener functionality for all batch events, use the following

0 commit comments

Comments
 (0)