anchor.diff:  
   There are two observable side-effects from the execution of this route.  Firstly, when the fake SOAP service is called, it should return an internal Id.  This, along with the rest of the message payload, are logged to the console:
   
  -image::images/050-camel-route-logging.png[width=800,height=469,link="images/050-camel-route-logging.png"]
  +image::images/050-camel-route-logging.png[width=800,height=469,link="https://raw.githubusercontent.com/isisaddons/isis-module-publishmq/master/images/050-camel-route-logging.png"]
   
   (The action identifier metadata that is added to the Camel header for routing has also been annotated).
   
   Second, because the fake SOAP service _is_ called, we can query it to check that the data was posted.  The screenshot below uses link:http://www.soapui.org/[SOAP UI], which can generate stub requests from the WSDL (available at http://localhost:8080/soap/SoapSubscriber/DemoObject?wsdl[http://localhost:8080/soap/SoapSubscriber/DemoObject?wsdl]):
   
  -image::images/060-query-fake-server.png[width=800,height=469,link="images/060-query-fake-server.png"]
  +image::images/060-query-fake-server.png[width=800,height=469,link="https://raw.githubusercontent.com/isisaddons/isis-module-publishmq/master/images/060-query-fake-server.png"]
   
   
   === Proxying the REST and SOAP calls
   
   To see in a little more detail what the `attachDtoFromRestfulObjects` and `postToFakeExternalSoapService` processors actually do, we can use the venerable link:http://ws.apache.org/tcpmon/download.cgi[tcpmon] to act as a proxy.  For example, we can set up port 6060 to forward onto port 8080:
   
  -image::images/110-proxy-restful-objects.png[width=800,height=469,link="images/110-proxy-restful-objects.png"]
  +image::images/110-proxy-restful-objects.png[width=800,height=469,link="https://raw.githubusercontent.com/isisaddons/isis-module-publishmq/master/images/110-proxy-restful-objects.png"]
   
   We can similarly do the same for port 7070, also forwarding onto port 8080.
   
  
positive.code: 
  Once connected we can navigate to the ActiveMQ tab:
  
  image::images/320-monitor-activemq.png[width=800,height=469,link="images/320-monitor-activemq.png"]
  
  and similarly to the Camel tab:
  
  image::images/330-monitor-camel.png[width=800,height=469,link="images/330-monitor-camel.png"]
  
  
  
  
negative.code: 
  The call to the fake SOAP service meanwhile is more straightforward: we observe just the regular SOAP messages (the implementation uses `wsdl2java` to create stubs, so the code is very straightforward):
  
  image::images/210-proxy-soapservice.png[width=800,height=469,link="https://raw.githubusercontent.com/isisaddons/isis-module-publishmq/master/images/210-proxy-soapservice.png"]
  
  === Jolokia and Hawt.io
  
  