I tried as per your suggestion like this:

from("jbi:service:http://servicemix.in2m.com/samples/http/jmsConsumer1";)
        .intercept(new DelegateProcessor() {
                      public void process(Exchange exchange) {
                          try {
                                  proceed(exchange);
                                 
exchange.setProperty("serviceName","http://servicemix.in2m.com/samples/http/MyProviderService";);
                                  ErrorEnrich.sendErrorToErrorHandler(exchange);
                          } catch (Exception e) {
                                                        e.printStackTrace();
                                                  }
                      };
                 
}).to("jbi:service:http://servicemix.in2m.com/samples/http/MyProviderService?mep=in-out";);
                 
But here I am manually setting the serviceName as the jbi service. i dont
want this. 

suppose I want to send the message to two sevices like this:

from("jbi:service:http://servicemix.in2m.com/samples/http/jmsConsumer1";)
        .intercept(new DelegateProcessor() {
                      public void process(Exchange exchange) {
                          try {
                                  proceed(exchange);
                                  ErrorEnrich.sendErrorToErrorHandler(exchange);
                          } catch (Exception e) {
                                                        e.printStackTrace();
                                                  }
                      };
                 
}).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";);

Then how can get the name of the sevice which causes error?Please help.

Pratibha

-- 
View this message in context: 
http://www.nabble.com/How-to-get-original-sevice-name-in-dead-letter-channel--tp18231948p18337002.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.

Reply via email to