fce2acb3fa
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://services.gradle.org/distributions/gradle- (404) with 1 occurrences migrated to: https://services.gradle.org/distributions/gradle- ([https](https://services.gradle.org/distributions/gradle-) 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 63 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 4 occurrences migrated to: https://www.apache.org/licenses/LICENSE-2.0 ([https](https://www.apache.org/licenses/LICENSE-2.0) result 200). * http://www.apache.org/licenses/LICENSE-2.0.txt with 64 occurrences migrated to: https://www.apache.org/licenses/LICENSE-2.0.txt ([https](https://www.apache.org/licenses/LICENSE-2.0.txt) result 200). * http://projects.spring.io/spring-integration with 64 occurrences migrated to: https://projects.spring.io/spring-integration ([https](https://projects.spring.io/spring-integration) result 301). * http://repo.spring.io/libs-milestone with 2 occurrences migrated to: https://repo.spring.io/libs-milestone ([https](https://repo.spring.io/libs-milestone) result 302). * http://repo.spring.io/libs-snapshot with 2 occurrences migrated to: https://repo.spring.io/libs-snapshot ([https](https://repo.spring.io/libs-snapshot) result 302). * http://repo.spring.io/libs-staging-local with 1 occurrences migrated to: https://repo.spring.io/libs-staging-local ([https](https://repo.spring.io/libs-staging-local) result 302). # Ignored These URLs were intentionally ignored. * http://maven.apache.org/POM/4.0.0 with 126 occurrences * http://www.w3.org/2001/XMLSchema-instance with 63 occurrences
JMS Sample
This example demonstrates the following aspects of the Java Message Service (JMS) support available with Spring Integration:
- JMS Message-driven Channel Adapter
- JMS Inbound Gateway
- JMS Outbound Gateway
It also uses the following components:
- Poller
- Stdout Channel Adapter (from Stream support Module)
- Stdin Channel Adapter (from Stream support Module)
- Aggregator
It also shows an example of using Spring profiles to modify the configuration for test cases.
The Stdout and Stdin Channel Adapters will allow you to interact with JMS via the console. It uses an embedded ActiveMQ broker.
To run the sample, simply execute the Main class located in the the org.springframework.integration.samples.jms package either from your favorite IDE or by using Gradle. When using Gradle you can start the sample by executing:
$ gradlew :jms:run
You will then be prompted to run one of three demos:
- GatewayDemo
- ChannelAdapterDemo
- AggregationDemo
The console output should look like:
=========================================================
Welcome to the Spring Integration JMS Sample!
For more information please visit:
http://www.springintegration.org/
=========================================================
16:48:21.158 INFO [org.springframework.integration.samples.jms.Main.main()][org.springframework.integration.samples.jms.ActiveMqTestUtils] Refreshing ActiveMQ data directory.
Which Demo would you like to run? <enter>:
1. Channel Adapter Demo
2. Gateway Demo
3. Aggregation Demo
When running any of the demos you will see the following prompt:
> Please type something and hit <enter>
- GatewayDemo uses the DemoBean service, which will echo the response and upper-casing it.
- ChannelAdapterDemo will simply echo the response
- AggregatingDemo uses a JMS Topic; and aggregates the responses from two inbound gateways, which invoke a flow that upper-cases the response; the aggregation returns a list of responses.
There are also test cases that exercise each demo; utilizing Spring 3.0 profiles to route the output to a QueueChannel instead of stdout.