| == Spring & Pulsar Example |
| |
| === Introduction |
| |
| This example shows how to work with the Camel-Pulsar Component. |
| |
| The example consumes messages from a topic and invoke the bean with the |
| received message. |
| |
| You can run the Pulsar cluster through docker: |
| |
| ---- |
| $ docker run -it \ |
| -p 6650:6650 \ |
| -p 8080:8080 \ |
| -v $PWD/data:/pulsar/data \ |
| apachepulsar/pulsar:latest \ |
| bin/pulsar standalone |
| ---- |
| |
| The Server is required to be running when you try the clients. |
| |
| And for the Client we have a total of three flavors: NB only 1st one |
| working at the moment - Normal use the ProducerTemplate ala Spring |
| Template style - Using Spring Remoting for powerful "Client doesn’t |
| know at all it's 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 |
| ---- |
| //Below don't work yet |
| //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/community/support/[let us know]. |
| |
| We also love contributors, so |
| https://camel.apache.org/community/contributing/[get involved] :-) |
| |
| The Camel riders! |
