camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dhiraj Bokde (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CAMEL-7399) Camel Salesforce integration tests fail with ClassNotFoundException
Date Mon, 28 Apr 2014 22:23:14 GMT

     [ https://issues.apache.org/jira/browse/CAMEL-7399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dhiraj Bokde resolved CAMEL-7399.
---------------------------------

    Resolution: Fixed

Fixed with commit 4fceb6a18cf57a5694a4d99be395b060e8bf3ea3

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

Mime
View raw message