Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (nike.apache.org: domain of raul@evosent.com designates
 209.85.160.53 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAGfr3_mc-KisR3-k3yD=V4sovnu7WJ8C4zTtTmgGgUQjO_fjEw@mail.gmail.com>
References: 
 <CAGfr3_mc-KisR3-k3yD=V4sovnu7WJ8C4zTtTmgGgUQjO_fjEw@mail.gmail.com>
From: Raul Kripalani <raul@evosent.com>
Date: Wed, 2 Apr 2014 11:27:33 +0100
Message-ID: 
 <CAKoNANs_tZ40h2MezbUSmYE1Aiq92MaSTEVs9CaM-=HrKmZJLQ@mail.gmail.com>
Subject: Re: Looking for ideas to reduce code volume and duplication
To: "users@camel.apache.org" <users@camel.apache.org>
Content-Type: multipart/alternative; boundary=047d7b86f4e6bcdbe804f60cbcbf

--047d7b86f4e6bcdbe804f60cbcbf
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Try this technique. Nothing fancy, just a plain old Java static helper
method. It relies on Camel being able to configure exception handlers if
placed at the end of the route definition, which I think is possible.
Please give it a spin and report back to the community!

public class RouteExceptionHandlerEnhancer {
   public static void enhance(RouteDefinition def) {
      def.onException(Exception.class).useOriginalMessage().handled(true)
 // catch exceptions
               .setHeader(Exchange.FAILURE_ROUTE_ID,
property(Exchange.FAILURE_ROUTE_ID))    // set route that errored
               .setHeader(Exchange.EXCEPTION_CAUGHT,
simple("${exception.stacktrace}"))
// Store reason for error
               .to(ExchangePattern.InOnly, endpointAMQ(config.
queueCaseAutomationDead()))
          .end();
   }
}


public class MyRoute extends RouteBuilder() {

    @Override
    public void configure() throws Exception {

       RouteDefinition route =3D
          from("direct:myendpoint")
              .log("Hello ${body")
              .to("activemq:queue:foo");

       RouteExceptionHandlerEnhancer.enhance(route);

    }

}

Regards,

*Ra=FAl Kripalani*
Apache Camel PMC Member & Committer | Enterprise Architect, Open Source
Integration specialist
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk

On Tue, Apr 1, 2014 at 3:51 PM, kraythe . <kraythe@gmail.com> wrote:

> Greetings:
>
> I have dozens of routes currently in our system and they have one of two
> variants of the following code:
>
>         .onException(Exception.class).useOriginalMessage().handled(true) =
//
> catch exceptions
> .setHeader(Exchange.FAILURE_ROUTE_ID, property(Exchange.FAILURE_ROUTE_ID)=
)
> // set route that errored
> .setHeader(Exchange.EXCEPTION_CAUGHT, simple("${exception.stacktrace}")) =
//
> Store reason for error
> .to(ExchangePattern.InOnly,
> endpointAMQ(config.queueCaseAutomationDead())).end() // to DLQ
>
> The problem is I am getting more than annoyed at having to copy paste thi=
s
> all over the place but since there are a couple of variants, I cant decla=
re
> a global handler. Making a direct is all well and good but doesnt really
> buy me much as I still have half the handler on every route.
>
> Any ideas how I could reduce code volume here ?
>
> *Robert Simmons Jr. MSc. - Lead Java Architect @ EA*
> *Author of: Hardcore Java (2003) and Maintainable Java (2012)*
> *LinkedIn: **http://www.linkedin.com/pub/robert-simmons/40/852/a39
> <http://www.linkedin.com/pub/robert-simmons/40/852/a39>*
>

--047d7b86f4e6bcdbe804f60cbcbf--