camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott Cranton (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-11111) Camel-Undertow: throwExceptionOnFailure doesn't work as expected
Date Fri, 07 Apr 2017 11:47:42 GMT

    [ https://issues.apache.org/jira/browse/CAMEL-11111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15960644#comment-15960644
] 

Scott Cranton commented on CAMEL-11111:
---------------------------------------

So my PR just includes a test case showing the issue with camel-undertow, and how camel-netty4-http
works doing similar settings of throwExceptionOnFailure. I could probably hack in the code
from camel-netty4-http and create a similar NettyHttpOperationsFailureException for camel-undertow
to band-aid this. It would only be an issue if many use ProducerTemplates to get the response
body back cast as a String or such, and expect any HTTP Response Code > 300 to be thrown
as an exception OR if they are using undertow as a producer within a camel route, and again
expect an exception to be thrown. I do the Producer Template approach a lot in test cases...

Since we're deprecating camel-http, and encouraging people to use camel-undertow as a producer,
that's where I think the expectation that it behaves similar will bite us...

Let me know your thoughts. Like I said, I believe I could quickly hack in something similar
to netty4-http that gets my test case to pass...

> Camel-Undertow: throwExceptionOnFailure doesn't work as expected
> ----------------------------------------------------------------
>
>                 Key: CAMEL-11111
>                 URL: https://issues.apache.org/jira/browse/CAMEL-11111
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-undertow
>    Affects Versions: 2.18.3
>            Reporter: Scott Cranton
>            Priority: Minor
>             Fix For: 2.19.0
>
>
> When using camel-undertow as a producer and HTTP_RESPONSE_CODE is 404, the producer does
NOT throw an exception as expected. Setting throwExceptionOnFailure appears to have no effect.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message