You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Denis Magda (JIRA)" <ji...@apache.org> on 2016/03/28 13:44:25 UTC
[jira] [Updated] (IGNITE-2899) BinaryObject is deserialized before
getting passed to CacheInterceptor
[ https://issues.apache.org/jira/browse/IGNITE-2899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Denis Magda updated IGNITE-2899:
--------------------------------
Summary: BinaryObject is deserialized before getting passed to CacheInterceptor (was: BinaryObject is deserialized before to get passed to CacheInterceptor)
> BinaryObject is deserialized before getting passed to CacheInterceptor
> ----------------------------------------------------------------------
>
> Key: IGNITE-2899
> URL: https://issues.apache.org/jira/browse/IGNITE-2899
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 1.5.0.final
> Reporter: Denis Magda
> Fix For: 1.6
>
>
> If {{CacheInterceptor}} is configured for a cache that stores {{BinaryObjects}} then the objects are always deserialized before being passed to the interceptor body.
> Attached test reveals the issue.
> In addition the test reproduces another bug when an object type is not being registered with {{BinaryContext}} if the object is being created with {{BinaryObjectBuilder}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)