GitHub user sirlatrom opened a pull request:
https://github.com/apache/camel/pull/1029
Add option to use String fields for picklists instead of enums
This change helps decoupling Salesforce picklist values from code using the
Camel Salesforce component. This allows writing custom business logic to handle
any discrepancies (e.g. extra/missing picklist values) instead of getting
deserializing exceptions.
Thus, when a new picklist value is added in Salesforce, running code will
not break just because the new value is not part of the corresponding enum.
Similarly, (feature toggled) business logic can be added to handle new
picklist values which have not yet been added to the corresponding Salesforce
object, e.g. due to different progressions in various staging environments
(*true story*).
Signed-off-by: Sune Keller <abs...@almbrand.dk>
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sirlatrom/camel
feature/option-use-strings-for-picklist-fields
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/1029.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1029
----
commit b632b788550f9da628dcbf2d9828711aca9b95a4
Author: Sune Keller <abs...@almbrand.dk>
Date: 2016-02-15T13:49:21Z
Add option to use String fields for picklists instead of enums
Signed-off-by: Sune Keller <abs...@almbrand.dk>
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
