What is the relationship between your camel route and the exception listener ?
If the example does not work anymore, this certainly means that the
listener does
something not compliant.  FYI, listeners can read or modify the
exchange, but can not
route it somewhere else, though it should be possible to do that by
sending a new
exchange to another component.

On Thu, May 22, 2008 at 7:27 AM, pratibhaG <[EMAIL PROTECTED]> wrote:
>
> I included the listener like this
> <sm:services>
>      <sm:statistics statsInterval="10" dumpStats="true" />
> </sm:services>
> <sm:listeners>
>        <bean id="errorBean" class="errorhandling.ExceptionListenerService"
> />
> </sm:listeners>
>
> and I tried this example:
> example: take a message from queue tutorial.camel.queue13 and pass it to a
> bean. The bean sets the message status to error. As the status is error the
> message is put in queue tutorial.camel.queue1
> here are some of the files of the example:
> jms-su xbean.xml
> <beans xmlns:jms="http://servicemix.apache.org/jms/1.0";
>       xmlns:esb="http://esbinaction.com/errorhandling";>
>
>  <jms:endpoint service="esb:errorHandlerDSL"
>       endpoint="errorEndpoint"
>       role="consumer"
>       destinationStyle="queue"
>       jmsProviderDestinationName="tutorial.camel.queue13"
>       defaultMep="http://www.w3.org/2004/08/wsdl/in-only";
>       connectionFactory="#connectionFactory"/>
>
>  <jms:endpoint service="esb:errorStorageService"
>       endpoint="errorStorageEndpoint"
>       role="provider"
>       destinationStyle="queue"
>       jmsProviderDestinationName="tutorial.camel.queue1"
>       defaultMep="http://www.w3.org/2004/08/wsdl/in-only";
>       connectionFactory="#connectionFactory"/>
>
>  <bean id="connectionFactory"
> class="org.apache.activemq.ActiveMQConnectionFactory">
>    <property name="brokerURL" value="tcp://localhost:61616" />
>  </bean>
>
> </beans>
>
> camel route builder java file
> package errorhandling.camel;
>
> import org.apache.camel.builder.RouteBuilder;
>
> public class CamelErrorHandler extends RouteBuilder {
>
>        private final static String NAMESPACE =
> "http://esbinaction.com/errorhandling";;
>        private final static String SERVICE_IN = "jbi:service:" +
>                NAMESPACE + "/errorHandlerDSL";
>        private final static String BEAN_IN = "jbi:service:" +
>                NAMESPACE + "/errorComponent";
>        private final static String ERROR_IN = "jbi:service:" +
>                NAMESPACE + "/errorStorageService";
>
>        public void configure() {
>
> /*errorHandler(deadLetterChannel(ERROR_IN).maximumRedeliveries(2));
>           from(SERVICE_IN).to(BEAN_IN);*/
>
> from(SERVICE_IN).errorHandler(deadLetterChannel(ERROR_IN).maximumRedeliveries(1)).to(BEAN_IN);
>            //from(SERVICE_IN).errorHandler(noErrorHandler).to(BEAN_IN);
>        }
> }
>
>
> Now if I don't put
> <sm:listeners>
>        <bean id="errorBean" class="errorhandling.ExceptionListenerService"
> />
> </sm:listeners>
>
> in conf/servicemix.xml then the example works fine. That is the message is
> consumed from tutorial.camel.queue13 and is routed to tutorial.camel.queue1
> as i am setting message status to error in my bean.
>
> But if I put
> <sm:listeners>
>        <bean id="errorBean" class="errorhandling.ExceptionListenerService"
> />
> </sm:listeners>
>
> in conf/servicemix.xml then the example does not work as expected.  That is
> the message is consumed from tutorial.camel.queue13 but not routed to
> tutorial.camel.queue1 even when  i am setting message status to error in my
> bean.
>
> Is it the same way the listener is supposed to behave or am I missing
> something.
>
> Another thing is that I never saw the message "The following error was
> caused by service"  which is created in my listener. Where this message will
> be shown?
>
> -Pratibha
>
>
>
> --
> View this message in context: 
> http://www.nabble.com/Exception-Listener-in-servicemix-tp15769242p17397607.html
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>
>



-- 
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/

Reply via email to