cc579226d6
- PR Comments - Switch to Jackson2 - Fix oxm config Polishing INTSAMPLES-127 Update to SI 4.0.0.RC1 INTSAMPLES-127 Remove Servlet Dependency travel sample; see INT-3350. INTSAMPLES-127 Update Samples to SI 4.0.0 JIRA: https://jira.spring.io/browse/INTSAMPLES-127 Created `maint` branch for ongoing SI 3.0.x samples.
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)
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 Maven. When using Maven you can start the sample by executing:
$ mvn clean package exec:java
You will then be prompted to run one of two demos:
- GatewayDemo
- ChannelAdapterDemo
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
When running either one 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
There are also test cases that exercise both demos; utilizing Spring 3.0 profiles to route the output to a QueueChannel instead of stdout.