Files
spring-cloud-task/spring-cloud-task-samples/batch-events
Glenn Renfro c7ef7fbff4 Starting to move to java 11[Do Not Merge]
All version changes are present.

Fixed all Java-Doc Errors and warnings

* Due to the stricter nature of the javadoc compiler we can't wrap <ul> / <ui> in <p>
* We will also need to Push up a test app for taklauncher to work with.   The old one fails to start now.   Or use one of the task starters possibly.
* Built on the work from TASK-439C.   Wait for that merge before merging this one.
* Replaced applicationFailedEvent class attribute with applicaitonFailedException
* Also polished the app used by the taskLauncherSink integration test
2018-11-01 15:23:17 -04:00
..
2018-11-01 10:45:15 -05:00
2016-04-25 23:05:07 -05:00
2016-04-25 23:05:07 -05:00

= Task Events

This is a task application that emits batch job events to the following channels:

	* job-execution-events
	* step-execution-events
	* chunk-events
	* item-read-events
	* item-process-events
	* item-write-events
	* skip-events

Note: More information on this topic is available https://docs.spring.io/spring-cloud-task/current-SNAPSHOT/reference/htmlsingle/#stream-integration-batch-events[here].

== Requirements:

* Java 7 or Above

== Build:

[source,shell,indent=2]
----
$ ./mvnw clean install
----

== Execution:

[source,shell,indent=2]
----
$ java -jar target/batch-events-1.2.1.RELEASE.jar
----

For example you can listen for specific job execution events on a specified channel with a Spring Cloud Stream Sink
like the log sink using the following:

[source,shell,indent=2]
----
$ java -jar <PATH_TO_LOG_SINK_JAR>/log-sink-rabbit-1.0.2.RELEASE.jar --server.port=9090
--spring.cloud.stream.bindings.input.destination=job-execution-events
----

== Dependencies:

The batch-events sample requires an instance of RabbitMQ to be running.