Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Standard JBI routing, for example, a binding component specifies a particular service engine to dispatch to, or the bus matches the Normalized Message XML content to a service's WSDL
  2. Content-based routing using XPath expressions on the Normalized Message XML content
  3. Additional Enterprise Integration Patterns related to routing
  4. Rules-driven routing using the servicemix-drools service engine
  5. Script-driven routing using the servicemix-script service engine
  6. Java code can perform routing using the servicemix-bean service engine
  7. You can drop in a JBI-compliant BPEL service engine (such as Ode to perform routing (among other things)

What transformation options does ServiceMix provide?

The main approach would be XSLT transformation on the Normalized Message XML content.

Additionally, many Many of the same options as in the routing answer above can be used for transformation. For example, messages can be transformed with XPath/XSLT, or via a script, or via a Java class, or BPEL, etc.

...

  • JBI routing, when configuration is needed, is configured in an XML file in the Service Unit
  • XPath /XSLT routing and transformation uses an entry in the XML file in the Service Unit
  • XSLT transformations use an entry in the XML file and a separate XSLT file in the Service Unit
  • Drools rules are typically defined in an XML file bundled in the Service Unit
  • Script-driven routing and transformation can use scripts in the XML file in the Service Unit
  • BPEL process definitions are packaged in the Service Unit

...

It is also possible to audit message traffic – one option would be to use XPath Routing the EIP WireTap to send each message to both an auditing service and the usual destination (or similarly, the Static Recipient List pattern). Another (if using the JMS Flow) would be to configure a virtual destination in ActiveMQ and audit copies of the message traffic.

...