You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Anton Vinogradov (JIRA)" <ji...@apache.org> on 2016/02/12 14:11:18 UTC

[jira] [Resolved] (IGNITE-2603) OSGi support for objects passed through CacheConfiguration

     [ https://issues.apache.org/jira/browse/IGNITE-2603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Anton Vinogradov resolved IGNITE-2603.
--------------------------------------
    Resolution: Fixed

All listed classes implemetations added to extdata/p2p.
Added new test uses these implementations via external classloader.

> OSGi support for objects passed through CacheConfiguration
> ----------------------------------------------------------
>
>                 Key: IGNITE-2603
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2603
>             Project: Ignite
>          Issue Type: Bug
>    Affects Versions: 1.5.0.final
>            Reporter: Denis Magda
>            Assignee: Anton Vinogradov
>             Fix For: 1.6
>
>
> If a user sets a custom class loader with {{IgniteConfiguration.setClassLoader}} then it always has to be used when the following objects passed to {{CacheConfiguration}} are being deserialized:
> - CacheStore factory;
> - CacheStoreSessionListener factory;
> - CachePluginConfiguration;
> - AffinityKeyMapper;
> - IgnitePredicate (as a node filter in CacheConfiguration.setNodeFilter(...));
> - CacheEntryListenerConfiguration class with factories for CacheEntryListener and CacheEntryEventFilter;
> In case of OSGi class loaders can be quite exotic. As an example {{CacheStore}} factory loaded from bundle A, can contain objects loaded from bundle B and bundle C. When such class loader is set as {{IgniteConfiguration.setClassLoader}} then deserialization of the {{CacheStore}} factory must work fine as well.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)