You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Jeremy Ross (Jira)" <ji...@apache.org> on 2021/11/16 19:49:00 UTC
[jira] [Commented] (CAMEL-13180) camel-salesforce - Apex calls could support more flexible response parsing
[ https://issues.apache.org/jira/browse/CAMEL-13180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17444765#comment-17444765 ]
Jeremy Ross commented on CAMEL-13180:
-------------------------------------
[~jsightle@redhat.com] does having HTTP response code/text solve this? See CAMEL-11078.
> 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)