ME properties in servicemix-eip

[Peter Klotz <pe...@blue-elephant-systems.com>]

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

Re: ME properties in servicemix-eip

[Guillaume Nodet <gn...@gmail.com>]

http://issues.apache.org/activemq/browse/SM-413

On 8/2/06, dkd <dk...@gmail.com> wrote:
>
>
> Was there a JIRA raised for this?
> --
> View this message in context:
> http://www.nabble.com/ME-properties-in-servicemix-eip-tf1517601.html#a5612193
> Sent from the ServiceMix - User forum at Nabble.com.
>
>


-- 
Cheers,
Guillaume Nodet

Re: ME properties in servicemix-eip

[dkd <dk...@gmail.com>]

Was there a JIRA raised for this?
-- 
View this message in context: http://www.nabble.com/ME-properties-in-servicemix-eip-tf1517601.html#a5612193
Sent from the ServiceMix - User forum at Nabble.com.

Re: ME properties in servicemix-eip

[Guillaume Nodet <gn...@gmail.com>]

Sure that would be nice.
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...)

Please raise a JIRA for that.
And attach a patch if you have time ;)

Cheers,
Guillaume Nodet

On 4/27/06, Peter Klotz <pe...@blue-elephant-systems.com> wrote:
> 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
>
>