You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2017/09/12 08:07:01 UTC

[jira] [Assigned] (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:all-tabpanel ]

Vladimir Ozerov reassigned IGNITE-5038:
---------------------------------------

    Assignee: Vladimir Ozerov  (was: Vladislav Pyatkov)

> 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: Improvement
>          Components: binary
>    Affects Versions: 2.0
>            Reporter: Dmitry Karachentsev
>            Assignee: Vladimir Ozerov
>              Labels: features
>             Fix For: 2.3
>
>         Attachments: results-compound-20170802.zip, results-compound-20170808.zip
>
>
> 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.4.14#64029)