[
https://issues.apache.org/jira/browse/CAMEL-13180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17445382#comment-17445382
]
Jeremy Ross commented on CAMEL-13180:
-------------------------------------
[~jsigh...@redhat.com] yeah that's not ideal. In the case of a non-2xx
response, I'd prefer to keep the original body intact for debugging and logging
purposes. That would be consistent with the other operations. But maybe the
apexCall operation is a special case. Maybe we always put the http response
body in a header?
> camel-salesforce - Apex calls could support more flexible response parsing
> --------------------------------------------------------------------------
>
> Key: CAMEL-13180
> URL: https://issues.apache.org/jira/browse/CAMEL-13180
> Project: Camel
> Issue Type: New Feature
> Components: camel-salesforce
> Reporter: Jesse Sightler
> Priority: Major
>
> The current approach requires following a very strict format for error codes
> other than 2xx. This isn't necessarily the case, though, for custom apex
> classes.
> Ideally, it would be possible to (optionally) handle the parsing in the camel
> route itself.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
