Hi Claus, I am sorry but I don't understand what you mean... would it be possible for you to send me a sample (just the route)
Claus Ibsen-2 wrote: > > Hi > > Interesting use case you got. > I got to go over this again at another time. I am at a business > convention in the US which means I am on a 9h timezone difference > which makes me a bit dizzy at this moment. > > However just wanted to pitch in that JMX stores performance stats for > nearly all processors in a Camel route. However I know the JMX API is > clumpsy and a pain in the ...... to use. > > Using the interceptSendToEndpoint appears at first sight convenient to > use in your situations but you need to have a hook to the after > sending which it does not provides currently. > > We may be able to add something to the DSL so you can control when to > send to the original designated endpoint. Currently we only get the > skipSendToOriginalEndpoint(). However you could use this fact and send > the message yourself. > > For example from a bean or processor you could just > > long start = .... > > // send to intended endpoint > String uri = exchange.getHeader(Exchange.INTERCEPTED_ENDPOINT, > String.class); > // use eg producer template to send to that uri > long end = ... > > And you can use try .. finally so the end is always computed. > > > -- View this message in context: http://old.nabble.com/recipientList-%2B-AggregationStrategy-tp27305176p27325684.html Sent from the Camel - Users mailing list archive at Nabble.com.
