> I also meant that if there is not, it should be added :-)
Ok... ;-)
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 t
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 operation also configurable on the endpoint (to be
> consistent
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 addit
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 a
