GitHub user dkhanolkar opened a pull request:
https://github.com/apache/camel/pull/617
Future proofing the LoginToken
Salesforce can potentially add new fields to their OAuth JSON output which
can break the LoginToken.java and we have to keep patching it on a regular
basis. Added a new class level annotation which ignores all new unrecognised
fields during json deserialisation. So, now we only need to patch the
LoginToken.java where we really need to use that new field. Added a test case
which demonstrates it.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dkhanolkar/camel master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/617.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 #617
----
commit b18d601e49abfe1eb5f90f0cb1719ee64c548aa4
Author: Devendra Khanolkar <[email protected]>
Date: 2015-09-16T11:16:05Z
Fix for login failure post Salesforce Non Prod patch
commit 227cc742282ab3de44600fe705150eefa1f0a8df
Author: Devendra Khanolkar <[email protected]>
Date: 2015-09-21T01:30:41Z
Added a fix to the LoginToken class to ensure future new SF fields dont
cause the login to fail, added a testcase for it
----
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
