Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (athena.apache.org: domain of raul@fusesource.com
 designates 74.125.245.76 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1337634818699-5713181.post@n5.nabble.com>
References: <1337278616469-5711530.post@n5.nabble.com>
 <1337634818699-5713181.post@n5.nabble.com>
From: Raul Kripalani <raul@fusesource.com>
Date: Tue, 22 May 2012 11:00:14 +0100
Message-ID: 
 <CAGgTx3gsbrDv3_iRPRpyD8hVKGXiXJ2ok8bvx4xKVZOvf2mazw@mail.gmail.com>
Subject: Re: Best practice to parse JSON response and retry if error
To: users@camel.apache.org
Content-Type: multipart/alternative; boundary=047d7b2ed3579456f304c09d1783

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

Have you tried encapsulating both the HTTP invocation + the JSON
unmarshalling behind a direct: endpoint? i.e.

from("direct:doHttpInvocation")
       .to("http://localhost:8088/?cmd=3Dls%20/tmp/unlock")
       .unmarshal().json(JsonLibrary.Jackson, ShellResponse.class);

The default error handler in this new route (DefaultErrorHandler) will
immediately return the exception to the caller.

>From the parent route, you invoke the direct endpoint using:
.to("direct:doHttpInvocation"). Hence, the two operations become one from
the viewpoint of the parent route, so it should now cycle over
"direct:doHttpInvocation" for redeliveries.

Let us know if that worked for you.

Regards,

*Ra=FAl Kripalani*
Principal Consultant | FuseSource Corp.
raul@fusesource.com | fusesource.com <http://www.fusesource.com/>
skype: raul.fuse | twitter: @raulvk <http://twitter.com/raulvk>,
@fusenews<http://twitter.com/fusenews>

<http://twitter.com/fusenews>


On 21 May 2012 22:13, Nestor Urquiza <nestor.urquiza@gmail.com> wrote:

> One way to solve this (successfully tested) would be using a bean
> encapsulating all the logic (http request, unmarshalling, testing for
> errors):
> <code>
> //So we are probably better just building a bean that invokes the http
> service, analyze the response and throws Exception if error
>        .setHeader("url",
> constant("http://localhost:8088/cmd=3Dls%20/tmp/unlock
> ")).bean(ShellBeanService.class)
> </code>
>
> I believe a nice feature would be to allow to go to a particular point in
> the case of a failure. I am unsure how to achieve that though.
>
> I would appreciate any feedback on this.
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Best-practice-to-parse-JSON-response-an=
d-retry-if-error-tp5711530p5713181.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>

--047d7b2ed3579456f304c09d1783--