Thank you -- That is helpful but actually I am converting getFromEndpoint
to a string and logging that, but I can stuff most of the information into
routeId. Also, since I can get to exchange via groovy, I can do anything
without resorting to writing a bean, just not conveniently as a one liner
in <log>.

~ cg

On Wed, Mar 18, 2015 at 1:00 PM, Claus Ibsen <[email protected]> wrote:

> There is a route id function
>
> ${routeId}
>
> See the functions in the table at
> http://camel.apache.org/simple
>
> On Wed, Mar 18, 2015 at 8:48 PM, Camel Guy <[email protected]> wrote:
> > Deep in the "message stack" I want to do this:
> >
> > <log message="Finished: ${exchange.getFromRouteId}">
> >
> > .. instead of putting the "from" routeId into a property or header, which
> > is what I was doing because I was ignorant of exchange.getFromRouteId.
> >
> > On Wed, Mar 18, 2015 at 12:30 PM, Claus Ibsen <[email protected]>
> wrote:
> >
> >> Hi
> >>
> >> No what is the use-case?
> >>
> >> On Wed, Mar 18, 2015 at 8:18 PM, Camel Guy <[email protected]> wrote:
> >> > ${exchange} doesn't seem to work
> >> >
> >> >
> >> > Thanks,
> >> > ~dg
> >>
> >>
> >>
> >> --
> >> Claus Ibsen
> >> -----------------
> >> Red Hat, Inc.
> >> Email: [email protected]
> >> Twitter: davsclaus
> >> Blog: http://davsclaus.com
> >> Author of Camel in Action: http://www.manning.com/ibsen
> >> hawtio: http://hawt.io/
> >> fabric8: http://fabric8.io/
> >>
>
>
>
> --
> Claus Ibsen
> -----------------
> Red Hat, Inc.
> Email: [email protected]
> Twitter: davsclaus
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen
> hawtio: http://hawt.io/
> fabric8: http://fabric8.io/
>

Reply via email to