Hi, in the routing patterns of servicemix-eip e.g. the content-based router, it seems that one cannot access ME properties only the ME content? Wouldn't it be a nice feature if one could e.g. set a property in a transformer component and make use of it in routing so that one has a bit of context information available in the patterns, not only the content? In the content-based router one could e.g. access properties by $name_of_property in the XPath expressions.
Peter
