bf88018d82
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 Multibinder Application with Different Systems This example shows how to run a Spring Cloud Stream application with two different binder types (Kafka and RabbitMQ) ## Running the application The following instructions assume that you are running Kafka and RabbitMQ as a Docker images. Go to the application root: * `docker-compose up -d` This brings up both Kafka and RabbitMQ clusters in docker containers. Local ports mapped are 9092 and 5672 for Kafka and RabbitMQ respectively. * `./mvnw clean package` The sample comes with a convenient test producer and consumer to see the processor in action. After running the program, watch your console, every second some data is sent to Kafka and it is received through RabbitMQ. ``` java -jar target/multibinder-0.0.1-SNAPSHOT.jar ``` You can also send data directly to Kafka topic: `docker exec -it kafka-multibinder /opt/kafka/bin/kafka-console-producer.sh --broker-list 127.0.0.1:9092 --topic dataIn` Enter some text and verify it comes through the console output (test consumer) You can also go the RabbitMQ UI: `http:localhost:15672` Once you are done testing: `docker-compose down`