When I send a message to "http://servicemix.in2m.com/samples/http/MyProviderService1" or "http://servicemix.in2m.com/samples/http/MyProviderService2" it may send Connection Exception and the message moves to "service:http://servicemix.in2m.com/samples/http/bean3Service".
The meaning with this is something we have a few tickets for already.
A kinda ExchangeContext where end-users and the camel framework itself can get hold on current execution route and other meta data information.
We need it in particular for encoding configuration so type converters etc. can get what to use for byte encodings.
Also the tracer logger should use this to get the "from" route so it can write:
from XXX -> process YYY
process YYY -> to(activemq:orders)
etc.
Claus Ibsen - 14/Jul/08 07:44 AM The meaning with this is something we have a few tickets for already.
A kinda ExchangeContext where end-users and the camel framework itself can get hold on current execution route and other meta data information.
We need it in particular for encoding configuration so type converters etc. can get what to use for byte encodings.
Also the tracer logger should use this to get the "from" route so it can write:
from XXX -> process YYY
process YYY -> to(activemq:orders)
etc.
A kinda ExchangeContext where end-users and the camel framework itself can get hold on current execution route and other meta data information.
We need it in particular for encoding configuration so type converters etc. can get what to use for byte encodings.
Also the tracer logger should use this to get the "from" route so it can write:
from XXX -> process YYY
process YYY -> to(activemq:orders)
etc.