You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Soann Dewasme (Jira)" <ji...@apache.org> on 2020/04/02 14:14:00 UTC
[jira] [Commented] (CAMEL-13181) camel-salesforce - rest exception
parsing produces useless messages
[ https://issues.apache.org/jira/browse/CAMEL-13181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17073769#comment-17073769 ]
Soann Dewasme commented on CAMEL-13181:
---------------------------------------
[~zregvart] I don't know how Salesforce work but I suppose we can have deeper look into errors, look what is Salesforce data format when error occurs and parsing it for "non-debug" mode. This way we can have an explicit message without sensitive data leak.
About capping, the problem is that we do not know if removed data overflow contains relevant information about a problem. So I suppose let all content is best choice in case of "debug" mode.
{{rawErrors}} seems a good naming.
I'll try to implement this
> camel-salesforce - rest exception parsing produces useless messages
> -------------------------------------------------------------------
>
> Key: CAMEL-13181
> URL: https://issues.apache.org/jira/browse/CAMEL-13181
> Project: Camel
> Issue Type: Improvement
> Components: camel-salesforce
> Reporter: Jesse Sightler
> Priority: Minor
>
> In the case of serialization failures, createRestException swallows the exception and logs the inputstream object itself:
>
> [https://github.com/apache/camel/blob/master/components/camel-salesforce/camel-salesforce-component/src/main/java/org/apache/camel/component/salesforce/internal/client/DefaultRestClient.java#L119]
>
> This does not tend to produce an error message, as the response is essentially always something like "ByteArrayInputStream@\{hashcode}". Perhaps it could try to return the raw contents if it is short and json?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)