For the inline use case, can we do away with the destination-name concept, it seems harder to use and doesn't add significant value. | <action class="org.jboss.soa.esb.actions.ContentBasedRouter" name="ContentBasedRouter"> | <property name="cbrClass" value="XPath"/> | <property name="ruleSet"> | <rule target-service="OrderCategory:BlueService" expression="/order/header[@cat='blue']" /> | <rule target-category="OrderCategory" target-service="RedService"" expression="/order/header[@cat='red']" /> | </property> | </action> | A couple of other points: I don't think "cbrClass" makes sense for the value of XPath but I don't have a better suggestion. I think property named "ruleSet" sounds a little strange for XPath users, since they have no knowledge of rules, just XPath expressions. One thing to keep in mind, XPath and/or Regex routers are the "default" router/wiretaper/filter, Rules-based routers will be considered the advanced options for only when the complexity rises to need that solution. Our Getting Started experience should start with XPath/Regex & XSLT with Rules-based CBR/Filter and Smooks-based Transformations being for more advanced use cases. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4256691#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...