You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@camel.apache.org by "Devendra Khanolkar (JIRA)" <ji...@apache.org> on 2015/09/21 04:03:04 UTC

[jira] [Created] (CAMEL-9149) Future proof the Salesforce LoginToken class

Devendra Khanolkar created CAMEL-9149:
-----------------------------------------

             Summary: Future proof the Salesforce LoginToken class
                 Key: CAMEL-9149
                 URL: https://issues.apache.org/jira/browse/CAMEL-9149
             Project: Camel
          Issue Type: Improvement
    Affects Versions: 2.12.0
            Reporter: Devendra Khanolkar
             Fix For: 2.16.0


Salesforce patch their instances once every quarter. So there's a good chance they might introduce a new JSON field in their OAuth response which might cause the login component to fall over. 
We can avoid that by adding a class level annotation which can suppress any failures that are caused due to 'new or unknown' fields. 
There's a pull request which fixes this along with a test case.
https://github.com/apache/camel/pull/617




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)