5148dabe5a
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 4 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/maven-4.0.0.xsd with 43 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://www.apache.org/licenses/LICENSE-2.0 with 66 occurrences migrated to: https://www.apache.org/licenses/LICENSE-2.0 ([https](https://www.apache.org/licenses/LICENSE-2.0) result 200). * http://repo.spring.io/libs-milestone-local with 2 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 2 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 1 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 86 occurrences * http://www.w3.org/2001/XMLSchema-instance with 43 occurrences
== Spring Cloud Stream Multibinder Application with Different Systems This example shows how to run a Spring Cloud Stream application with the same binder type configured for two separate Kafka clusters. ## Running the application The following instructions assume that you are running Kafka as a Docker image. * Go to the application root * `docker-compose up -d` This brings up two Kafka clusters in docker containers. Local ports mapped for kafka are 9092 and 9093 (Zookeeper local parts mapped are 2181 and 2182). * `./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 cluster 1 and it is received through Kafka cluster 2. To run the example, command line parameters for the Zookeeper ensembles and Kafka clusters must be provided, as in the following example: ``` java -jar target/multibinder-differentsystems-0.0.1-SNAPSHOT.jar --kafkaBroker1=localhost:9092 --zk1=localhost:2181 --kafkaBroker2=localhost:9093 --zk2=localhost:2182 ``` Alternatively, the default values of `localhost:9092` and `localhost:2181` can be provided for both clusters. Assuming you are running two dockerized Kafka clusters as above. Issue the following commands: `docker exec -it kafka-multibinder-1 /opt/kafka/bin/kafka-console-producer.sh --broker-list 127.0.0.1:9092 --topic dataIn` On another terminal: `docker exec -it kafka-multibinder-2 /opt/kafka/bin/kafka-console-consumer.sh --bootstrap-server 127.0.0.1:9093 --topic dataOut` Enter some text on the first one and the same text appears on the second one.