You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Guillaume Nodet (JIRA)" <ji...@apache.org> on 2006/09/29 10:45:25 UTC
[jira] Updated: (SM-413) access message exchange properties in e.g.
content-based routing XPath expressions of servicemix-eip
[ https://issues.apache.org/activemq/browse/SM-413?page=all ]
Guillaume Nodet updated SM-413:
-------------------------------
Fix Version/s: (was: 3.0.1)
> access message exchange properties in e.g. content-based routing XPath expressions of servicemix-eip
> ----------------------------------------------------------------------------------------------------
>
> Key: SM-413
> URL: https://issues.apache.org/activemq/browse/SM-413
> Project: ServiceMix
> Issue Type: Improvement
> Components: servicemix-eip
> Affects Versions: 3.0.1
> Reporter: Peter Klotz
>
> 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.
> It would 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.
> There are two ways to implement that:
> * create a custom predicate that can check a property on the
> exchange (with a regular expression maybe)
> * create an xpath function, configure it on the XPathPredicate and write
> a xpath expression using it
> The first one is easier of course and it could be combined with an
> xpath expression by implementing boolean predicates (or, and, xor,
> not...)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira