This commit updates URLs to prefer the https protocol. Redirects are not followed to avoid accidentally expanding intentionally shortened URLs (i.e. if using a URL shortener). # Fixed URLs ## Fixed But Review Recommended These URLs were fixed, but the https status was not OK. However, the https status was the same as the http request or http redirected to an https URL, so they were migrated. Your review is recommended. * [ ] http://packages.confluent.io/maven/ (404) with 7 occurrences migrated to: https://packages.confluent.io/maven/ ([https](https://packages.confluent.io/maven/) result 404). ## Fixed Success These URLs were switched to an https URL with a 2xx status. While the status was successful, your review is still recommended. * [ ] http://maven.apache.org/xsd/assembly-1.1.2.xsd with 6 occurrences migrated to: https://maven.apache.org/xsd/assembly-1.1.2.xsd ([https](https://maven.apache.org/xsd/assembly-1.1.2.xsd) result 200). * [ ] http://maven.apache.org/xsd/maven-4.0.0.xsd with 60 occurrences migrated to: https://maven.apache.org/xsd/maven-4.0.0.xsd ([https](https://maven.apache.org/xsd/maven-4.0.0.xsd) result 200). * [ ] http://repo.spring.io/libs-milestone-local with 4 occurrences migrated to: https://repo.spring.io/libs-milestone-local ([https](https://repo.spring.io/libs-milestone-local) result 302). * [ ] http://repo.spring.io/libs-release-local with 1 occurrences migrated to: https://repo.spring.io/libs-release-local ([https](https://repo.spring.io/libs-release-local) result 302). * [ ] http://repo.spring.io/libs-snapshot-local with 4 occurrences migrated to: https://repo.spring.io/libs-snapshot-local ([https](https://repo.spring.io/libs-snapshot-local) result 302). * [ ] http://repo.spring.io/release with 2 occurrences migrated to: https://repo.spring.io/release ([https](https://repo.spring.io/release) result 302). # Ignored These URLs were intentionally ignored. * http://maven.apache.org/POM/4.0.0 with 120 occurrences * http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2 with 12 occurrences * http://www.w3.org/2001/XMLSchema-instance with 66 occurrences
Spring Cloud Stream Reactive Processor Basic Sample ================================================== This is a Spring Cloud Stream reactive processor sample. ## Requirements To run this sample, you will need to have installed: * Java 8 or Above ## Running the application The following instructions assume that you are running Kafka as a Docker image. * Go to the application root (not the repository root, but this application) * `docker-compose up -d` * `./mvnw clean package` * `java -jar target/reactive-processor-0.0.1-SNAPSHOT.jar` The main application contains the reactive processor that receives textual data for a duration and aggregates them. It then sends the aggregated data through the outbound destination of the processor. The application also provides a source and sink for testing. Test source will generate some text every second and the test sink will verify that the processor has accumulated the text over a duration. Test source is bound to the same broker destination where the processor is listening from. Similarly test sink is bound to the same broker destination where the processor is producing to. You will see output similar to the following on the console every 5 seconds. ``` Data received: foobarfoobarfoo Data received: barfoobarfoobar Data received: foobarfoobarfoo Data received: foobarfoobarfoo ``` * `docker-compose down` ## Running the application using Rabbit binder All the instructions above apply here also, but instead of running the default `docker-compose.yml`, use the command below to start a Rabbitmq cluser. * `docker-compose -f docker-compose-rabbit.yml up -d` * `./mvnw clean package -P rabbit-binder` * `java -jar target/reactive-processor-0.0.1-SNAPSHOT.jar` Once you are done testing: `docker-compose -f docker-compose-rabbit.yml down`