[
https://issues.apache.org/jira/browse/IGNITE-5038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16457449#comment-16457449
]
Vyacheslav Daradur commented on IGNITE-5038:
--------------------------------------------
Hi, [~vozerov], [~v.pyatkov],
I have a use case where classes descriptions are owned by different
classloaders.
I have to serialize objects myself and use {{IgniteCache}} via
{{withKeepBinary}} mode in this case.
Completion of this task will allow us to use Ignite's serialization via
efficient {{BinaryMarshaller}} and significantly improve performance.
As far as I can see you have prepared the solution, are you going to merge it?
> 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
> Priority: Major
> Labels: features
> Fix For: 2.6
>
> 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
(v7.6.3#76005)
