[
https://issues.apache.org/activemq/browse/CAMEL-2519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=58022#action_58022
]
Willem Jiang commented on CAMEL-2519:
-------------------------------------
@Claus,
That is the side effect which we let the user to override the response code
when the exception is thrown.
The solution that I have is to remove the "Exchange.HTTP_RESPONSE_CODE" header
after the http endpoint or adding the below code in the route
{code}
onException(IllegalArgumentException.class).setOutHeader(Exchange.HTTP_RESPONSE_CODE,
constant(HttpServletResponse.SC_INTERNAL_SERVER_ERROR));
{code}
> camel-jetty - When returning an exception then allow to use custom http error
> code from Exchange.HTTP_RESPONSE_CODE
> -------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-2519
> URL: https://issues.apache.org/activemq/browse/CAMEL-2519
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-jetty
> Affects Versions: 2.2.0
> Reporter: Claus Ibsen
> Assignee: Willem Jiang
> Priority: Minor
> Fix For: 2.3.0
>
>
> By default camel-jetty will use http error code 500. But end user may
> override and set a specific error code to use instead
> See nabble:
> http://old.nabble.com/Return-exception-message-in-HTTP-body-ts27757151.html
> For example in DSL directly
> {code}
> onException(ValidationException).setHeader(Exchange.HTTP_RESPONSE_CODE,
> constant(HttpServletResponse.SC_BAD_REQUEST));
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
