You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Valentin Kulichenko (JIRA)" <ji...@apache.org> on 2015/12/12 02:26:46 UTC
[jira] [Resolved] (IGNITE-2095) SpringCacheManager doesn't support
withKeepBinary() flag
[ https://issues.apache.org/jira/browse/IGNITE-2095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Valentin Kulichenko resolved IGNITE-2095.
-----------------------------------------
Resolution: Won't Fix
Adding this to Spring Caching doesn't make much sense, because switching {{withKeepBinary}} flag on will force user to work with Ignite's {{BinaryObject}}, which eliminates advantages of cache abstraction. In this case it's easier to fully switch to Ignite API.
> SpringCacheManager doesn't support withKeepBinary() flag
> --------------------------------------------------------
>
> Key: IGNITE-2095
> URL: https://issues.apache.org/jira/browse/IGNITE-2095
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Reporter: Valentin Kulichenko
> Assignee: Valentin Kulichenko
> Priority: Critical
> Fix For: 1.5
>
>
> Currently {{SpringCacheManager}} doesn't allow to switch to {{withKeepBinary()}} cache.
> SO thread: http://stackoverflow.com/questions/34049172/ignite-and-spring-with-multiple-class-loaders/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)