| == Spring & JMS Example |
| |
| === Introduction |
| |
| This example shows how to work with the Camel-JMS Component. |
| |
| The example consumes messages from a queue and invoke the bean with the |
| received message. |
| |
| The Server is required to be running when you try the clients. |
| |
| And for the Client we have a total of three flavors: - Normal use the |
| ProducerTemplate ala Spring Template style - Using Spring Remoting for |
| powerful ``Client doesn’t know at all its a remote call'' - And using |
| the Message Endpoint pattern using the neutral Camel API |
| |
| === Build |
| |
| You will need to compile this example first: |
| |
| .... |
| mvn compile |
| .... |
| |
| === Run |
| |
| The example should run if you type: |
| |
| ==== Step 1: Run Server |
| |
| .... |
| mvn exec:java -PCamelServer |
| .... |
| |
| ==== Step 2: Run Clients |
| |
| .... |
| mvn exec:java -PCamelClient |
| mvn exec:java -PCamelClientRemoting |
| mvn exec:java -PCamelClientEndpoint |
| .... |
| |
| To stop the example hit ctrl+c |
| |
| === Help and contributions |
| |
| If you hit any problem using Camel or have some feedback, then please |
| https://camel.apache.org/support.html[let us know]. |
| |
| We also love contributors, so |
| https://camel.apache.org/contributing.html[get involved] :-) |
| |
| The Camel riders! |
