Skip to content
This repository has been archived by the owner on Jan 30, 2025. It is now read-only.

Latest commit

 

History

History
64 lines (34 loc) · 2.19 KB

README.md

File metadata and controls

64 lines (34 loc) · 2.19 KB

###Camel and CXF demo

This demo shows a frontend REST service that sends messages through a Content Based Router that routes messages either to a backend REST service, or a backend SOAP service depending on the message content.

alt text

To try it out point your browser at:

####Call the backend SOAP Service http://localhost:9090/route/restservice/getsomething/callSoapService

####Call the backend REST Service http://localhost:9090/route/restservice/getsomething/callRestService

####Demo Steps

  1. Before the demo, delete just the route from the blueprint.xml. Also start Fuse and execute fabric:create

  2. Create the route

  3. Run the unit test (right-click pom.xml > Run as... > Maven Tests

  4. Run on Local Camel Context (right-click blueprint.xml > Run as... > Local Camel Context without tests

  5. Enable tracing

  6. Exercise the route from a browser using the URL's above and show the message tracing

  7. IMPORTANT make sure you stop the Local Camel Context

  8. Deploy to Fabric. Open a terminal in the demo directory and execute mvn fabric8:deploy -DskipTests

  9. Open the Fuse Management Console

  10. Show the new Profile in the Wiki

  11. Create a new container using the new Profile

  12. Show the three services in the API tab and the WADL form for calling the services

  13. Connect to the container and show the Camel tab etc

  14. Enable Debugging and insert a breakpoint

  15. Exercise the route via the WADL in the API tab

  16. Step through the route and show the message state

  17. Go back to the IDE and modify the route by adding a Log message somewhere

  18. Edit the pom.xml at the end and change to version 2.0

  19. Re-deploy the new version by executing mvn fabric8:deploy -DskipTests

  20. Open the Manage tab in the Fabric

  21. Select version 2.0 and apply it to the container

  22. Show the new version 2.0 services in the API tab and the new route in the container

  23. Exercise version 2.0 from the WADL

  24. Show the revised route in the container and the new log message appearing