[
https://issues.apache.org/jira/browse/CAMEL-13180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse Sightler updated CAMEL-13180:
-----------------------------------
Description:
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.
was:
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 handle the parsing in the camel route itself.
> Camel 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
(v7.6.3#76005)
