anchor.diff:  
   == Application walk-through
   
  -The following screenshots show how the publishing service publishes the action invocation event that is then routed through to the (fake) external system using Camel:
  +The following screenshots show how the publishing service publishes the member interaction events that are then routed
  +through to the (fake) external system using Camel.
   
   === Installing the Fixture Data
   
  
positive.code:   </route>
  </camelContext>
  ----
  <1> subscribe to ActiveMQ for incoming action invocation events (in XML form).  This uses the internal `vm://` protocol for speed
  <2> unmarshal to a (JAXB annotated) `InteractionDto` object
  <3> using the `AddExchangeHeaders` component provided by this module to add the metadata from the `InteractionDto` to the Camel message.  This allows the message to be routed
  <4> use Camel to select which sub-route to following, using...
  
negative.code: 
  image:https://travis-ci.org/isisaddons/isis-module-publishmq.png?branch=master[Build Status,link=https://travis-ci.org/isisaddons/isis-module-publishmq]
  
  This module, intended for use with http://isis.apache.org[Apache Isis], provides an implementation of Apache Isis` link:http://isis.apache.org/guides/rg.html#_rg_services-spi_manpage-PublishingService[`PublishingService`] SPI that submits an XML representation of an link:https://github.com/apache/isis/blob/master/core/schema/src/main/resources/org/apache/isis/schema/ixn/ixn.xsd[`MemberInteractionDto`]s to an link:http://activemq.apache.org[ActiveMQ] queue.
  
  The example app itself also demonstrates how this member interaction event (action invocation or property edit) can
  be routed using link:http://camel.apache.org[Apache Camel]:
  
  * the payload is enriched using Apache Isis' own link:http://isis.apache.org/guides/ug.html#_ug_restfulobjects-viewer[Restful Objects] viewer (obtaining additional information).
  * the enriched message is used to post to a (fake) external SOAP, eg representing a General Ledger.
  