Looking good guys! Only two other things I'd like to see here. One is something similar to what someone else mentioned - basically allow the service name and category to optionally be xpath as well (basically destinations can be dynamic rather than picked from a static list). For example: <destination target-category="/order/header/@category" target-service="/order/header/@service" expression="/order/header[@cat='red']/> In this case, a previous action would have been responsible to set these attributes in the message or the other ESB service developers would be responsible to name the ESB services based on values already passed in the ESB message. Second thing is that I'd like the xpath to not be restricted to the default message body. Would be nice to be able to pull this data (decision expression or service name or service category ) from some place other than just the default message body. These same requests would apply to the regex router. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4256763#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...