You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Dhiraj Bokde (JIRA)" <ji...@apache.org> on 2014/04/29 00:17:18 UTC

[jira] [Created] (CAMEL-7399) Camel Salesforce integration tests fail with ClassNotFoundException

Dhiraj Bokde created CAMEL-7399:
-----------------------------------

             Summary: Camel Salesforce integration tests fail with ClassNotFoundException
                 Key: CAMEL-7399
                 URL: https://issues.apache.org/jira/browse/CAMEL-7399
             Project: Camel
          Issue Type: Bug
          Components: camel-salesforce
    Affects Versions: 2.13.0
            Reporter: Dhiraj Bokde
            Priority: Critical
             Fix For: 2.13.1


An upgrade to XStream version has broken the alias cache manipulation in XmlRestProcessor. Earlier versions of XStream used to only throw a ClassNotFoundException when CachingMapper.realClass call failed to find a mapped class, but recent versions now add the exception to its cache. This makes it imperative that the cache be flushed when no real class is found. As a result, the cache lookup optimization now only avoids flushing in case the alias mapping hasn't changed, which still works for repeated invocation of the same endpoint which requires using an XML alias for Salesforce's RESTish API. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)