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

Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2015/09/21 13:35:04 UTC

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

    [ https://issues.apache.org/jira/browse/CAMEL-9149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14900531#comment-14900531 ] 

Claus Ibsen commented on CAMEL-9149:
------------------------------------

[~dhirajsb] do you mind taking a look at this?

> 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)