AW: Possible Solution to a camel serviceengine problem or only a bad workaround??

please also see: https://issues.apache.org/activemq/browse/SM- this is the summary ;-) -Ursprüngliche Nachricht- Von: Guillaume Nodet [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 18. Oktober 2007 13:19 An: [EMAIL PROTECTED] Betreff: Re: Possible Solution to a camel

Re: Possible Solution to a camel serviceengine problem or only a bad workaround??

On 18/10/2007, Guillaume Nodet [EMAIL PROTECTED] wrote: The attachment was removed from your mail i suppose. Maybe just raise a jira and attach it there. Anyway, I think you're on the right track. There's no reason why the camel SE would set the jbi.operation property when going from jbi to

Possible Solution to a camel serviceengine problem or only a bad workaround??

Hi all I found a solution for my problem regarding the routing problem yesterday (http://www.nabble.com/How-to-route-a-MessageExchange-using-camel-to-ode-tf4641042s12049.html#a13255218). I wasn't able to route a message coming over HTTP Binding through camel to ODE service engine. I specified

Re: Possible Solution to a camel serviceengine problem or only a bad workaround??

The attachment was removed from your mail i suppose. Maybe just raise a jira and attach it there. Anyway, I think you're on the right track. There's no reason why the camel SE would set the jbi.operation property when going from jbi to camel, but not use it when going from camel to jbi. In

Re: Possible Solution to a camel serviceengine problem or only a bad workaround??

On 10/18/07, Kristian Köhler [EMAIL PROTECTED] wrote: Hi Anyway, I think you're on the right track. There's no reason why the camel SE would set the jbi.operation property when going from jbi to camel, but not use it when going from camel to jbi. In addition, we could make the

AW: Possible Solution to a camel serviceengine problem or only a bad workaround??

I also meant that if there is not, it should be added :-) Ok... ;-)