Hi Luqman,
ExtensionRegistry is used by IgnitePluginProcessor to replace internal
Ignite interface implementations, but it's only used for MessageFormatter,
MessageFactory and IoPool (search usages for
IgnitePluginProcessor#extensions). So if you do not want to use your own
implementation for that interfaces, you may omit using of ExtensionRegistry.
Yes, PluginProvider#plugin returns your plugin implementation that will be
accessible over Ignite.plugin("pluginName") at any place:
MyPlugin plugin = ignite.plugin("pluginName");
plugin.doCoolStuff();
PluginProvider#createComponent components that could be replaced by plugin
that I found for 2.0:
GridSecurityProcessor
DiscoveryNodeValidationProcessor
GridSegmentationProcessor
IgniteCacheObjectProcessor
PlatformProcessor
IgniteCacheDatabaseSharedManager
IgnitePageStoreManager
IgniteWriteAheadLogManager
CacheConflictResolutionManager
Thanks!
-Dmitry.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Ignite-PlugingProvider-tp14640p14885.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
