History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: CAMEL-699
Type: New Feature New Feature
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: pratibha
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Apache Camel

provide a feature to get the destination name in case of error

Created: 11/Jul/08 04:32 AM   Updated: 14/Jul/08 07:44 AM
Component/s: None
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Not Specified


 Description  « Hide
I have configuration like this:
exception(java.lang.Throwable.class)
.to("jbi:service:http://servicemix.in2m.com/samples/http/bean3Service?mep=in-out")
.to("jbi:service:http://servicemix.in2m.com/samples/http/bean2Service?mep=in-out");

from("jbi:service:http://servicemix.in2m.com/samples/http/httpConsumer")
.to("validator:updatepassword.xsd")
.to("jbi:service:http://servicemix.in2m.com/samples/http/jmsProviderService?mep=in-only")
.to("jbi:service:http://servicemix.in2m.com/samples/http/bean2Service");

from("jbi:service:http://servicemix.in2m.com/samples/http/jmsConsumer")
.to("jbi:service:http://servicemix.in2m.com/samples/http/MyProviderService1?mep=in-out")
.to("jbi:service:http://servicemix.in2m.com/samples/http/MyProviderService2?mep=in-out");

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".

Now in "service:http://servicemix.in2m.com/samples/http/bean3Service" there should a way to know which service was down, either "service:http://servicemix.in2m.com/samples/http/MyProviderService1" or "service:http://servicemix.in2m.com/samples/http/MyProviderService2"?



 All   Comments   Work Log   Change History   Subversion Commits   FishEye   Crucible      Sort Order: Ascending order - Click to sort in descending order
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.