You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladislav Pyatkov (JIRA)" <ji...@apache.org> on 2017/05/26 09:04:04 UTC

[jira] [Commented] (IGNITE-5038) BinaryMarshaller might need to use context class loader for deserialization

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

Vladislav Pyatkov commented on IGNITE-5038:
-------------------------------------------

I heave add ability to customize class loader when deserialize object from binary.
Added method {{BinaryObject#deserialize(java.lang.ClassLoader)}}.

Lock at my PR:
https://github.com/apache/ignite/pull/2011

Now the fix is testing on TC

> BinaryMarshaller might need to use context class loader for deserialization
> ---------------------------------------------------------------------------
>
>                 Key: IGNITE-5038
>                 URL: https://issues.apache.org/jira/browse/IGNITE-5038
>             Project: Ignite
>          Issue Type: New Feature
>          Components: cache
>    Affects Versions: 2.0
>            Reporter: Dmitry Karachentsev
>            Assignee: Vladislav Pyatkov
>              Labels: features
>             Fix For: 2.1
>
>
> There is a special use case discussed on the dev list:
> http://apache-ignite-developers.2346864.n4.nabble.com/Re-BinaryObjectImpl-deserializeValue-with-specific-ClassLoader-td17126.html#a17224
> According to the use case, BinaryMarshaller might need to try to deserialize an object using a context class loader if it failed to do so with a custom classloader (`IgniteConfiguration.getClassLoader()`) or the system one.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)