Hi Nick,
Unfortunately there is no way to use custom class loader without hacks
with internal API. I've opened a ticket for this feature [1], it could
be useful in such cases, please check.
[1] https://issues.apache.org/jira/browse/IGNITE-5038
Thanks!
-Dmitry.
19.04.2017 20:09, npordash пишет:
Thanks, Dmitry!
This is using Ignite 1.9. The stack trace is pretty straight forward:
Putting things into caches works just fine (f.e. instances of that Namespace
class), but pulling them out does not since the cache is only taking
Ignite's classloader into account. For the time being I've had to resort to
a hack where read operations use a binary view of the cache and then I have
to cast entries to BinaryObjectImpl or BinaryObjectOffheapImpl in order to
access (or copy) the backing array and then delegate to
Marshaller.unumarshal(byte[], ClassLoader) so the class can be found.
-Nick
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/BinaryObjectImpl-deserializeValue-with-specific-ClassLoader-tp12055p12087.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
