This repository has been archived by the owner on Jul 24, 2024. It is now read-only.
Add null checks to Salesforce connectors #307
Assignees
Labels
Milestone
Comments
syndesis-bot
added
cat/bug
zregvart
added a commit
to zregvart/syndesis
that referenced
this issue
Dec 18, 2017
This refactors Salesforce connectors to make them more maintainable and applicable for connector simplification planned next. Changes: - salesforce-upsert-contact-connector has been removed, we have a generic create or update connector for Salesforce - `salesforce-model` has been renamed to `salesforce-common` it used to contain only a DTO class, then expanded into containing base classes - all connectors are now based on a set of common base classes in `syndesis-common`, this should allow easier maintenance of the all Salesforce based connectors, and easy transition to simplified connector model in the future Fixes syndesisio#307, syndesisio#668
paoloantinori
pushed a commit
that referenced
this issue
May 23, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Seems that the body from the exchange can sometimes be
null, we need to guard from that in afterProcessors in Salesforce connectorsThe text was updated successfully, but these errors were encountered: