camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <>
Subject Re: Restlet Component Fault Handling
Date Thu, 26 Feb 2009 06:05:37 GMT
On Tue, Feb 24, 2009 at 1:21 AM, tfredrich <> wrote:
> I'm utilizing the Restlet component (via a Trunk build) and am interested in
> better understanding error handling behavior via the exchange fault message.
> BTW, I appreciate your work on this component!  Good stuff, indeed.
> In essence, I'm simply using camel-restlet to expose a JSON RESTful service
> with CRUD behavior.  The route looks something like this:
> from("restlet:http://localhost:8080/people/person/{userId}?restletMethod=GET")
>    .intercept(new AuthenticationInterceptor())
>    .process(new QueryStringProcessor())
>    .process(new GetPersonProcessor())
>    .marshal(format)
>    .process(new JsonpProcessor());
> Of interest for my question is the GetPersonProcessor, which is responsible
> for retrieving the person object from a storage repository.  When a
> non-existent userId is requested, the GetPersonProcessor does not return a
> person object and, instead sets the restlet response header to 404 (not
> found).  After reading the Camel manual, I thought it best to set the 404
> along with a fault message on the exchange, but the restlet component
> doesn't appear to acknowledge the fault and composes its response from the
> out message.  So, unless I misunderstand, I have to set the 404 on the out
> message header (for the restlet component) and set the body on the fault
> message (for camel to terminate the pipeline).
> Now for the question:  Is this the way I should be doing things?  Or
> could/should the DefaultRestletBinding utilize the fault message to compose
> its response, if a fault message exists?  Your feedback is much appreciated.

William Tam or William Jiang is the people behind the camel-restlet component
and will be able to help you.

Whats you current status?

The fault stuff in Camel is put in Camel because of JBI. In pure camel
its not really used as we use Exceptions to indicate failures.
So there can be a few rough spots in the some components that does not
adhere to fault.

And take a look in the source code for restlet. Compare it with
camel-http that should honor the fault stuff.
You might find a gremlin and can point out the problem so we can fix it faster.

> Thanks,
> --Todd
> --
> View this message in context:
> Sent from the Camel - Users (activemq) mailing list archive at

Claus Ibsen
Apache Camel Committer

Open Source Integration:

View raw message