[
https://issues.apache.org/jira/browse/IGNITE-5038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16116521#comment-16116521
]
Vladimir Ozerov commented on IGNITE-5038:
-----------------------------------------
[~v.pyatkov], I understand the solution in general, but there are several
comments from my side at the moment:
1) I am strongly against any {{ClassLoader}} and/or {{Class}} caches.
{{IgniteUtils.weakCache}} must go away. We had too many problems with such
caches before. So just don't.
2) {{IgniteUtils}} doesn't compile on my machine. Are sure you have Java 7
compilation level set in IDE?
3) {{OptimziedObjectStreamRegistry.in}} - if {{useCache == false}}, then we
cannot use {{inPool}}, are we?
> 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.2
>
> Attachments: results-compound-20170802.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)
