Hello,
By reviewing a backlog items related to Ignite I found that in one case
we've ran into a classloading problem visible with thin client calling
a compute task.
It seems that currently there is no way for give a thin client
classloader which should be used by it to resolve received payloads. In
our case we send type X and receive type Y which is available in a thin
client caller, but not known to ignite at all. Because thin client has
no way to know type Y and have no option to inject class loader, it
reverts back to its own classloader.
Issue I speak about is visible only under OSGi which uses multiple
classloaders, it does not affect ie. spring/webapps or other flat
classpath deployments. Effectively for OSGi each JAR ends up with its
own classloader which limits its access only to dependencies declared in
manifest (through import-package manifest entry).
From notes I collected - thin client configuration has no ways to
provide a classloader used for type resolution. It is opposite of what
is possible with `IgniteConfiguration` which we utilize with a success
under OSGi.
I am not sure if there is a way around the issue with ie. custom
marshaller or its configuration. In any case I am able to provide a
complete stacktrace for ignite 2.14 to register jira ticket and trace
down issue.
Best,
Łukasz
