[ https://issues.apache.org/jira/browse/IGNITE-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15754219#comment-15754219 ]
Vladimir Ozerov commented on IGNITE-4441: ----------------------------------------- Pavel, Please note that we must not only call a single "start" method, but rather wire-up the plugin with general start lifecycle: - onStart - onIgniteStart - onIgniteStop - onStop > Define plugin API in .NET > ------------------------- > > Key: IGNITE-4441 > URL: https://issues.apache.org/jira/browse/IGNITE-4441 > Project: Ignite > Issue Type: Sub-task > Components: platforms > Reporter: Pavel Tupitsyn > Assignee: Pavel Tupitsyn > Labels: .NET > Fix For: 2.0 > > > Define plugin API in .NET similar to Java API: > * {{IgniteConfiguration.PluginConfigurations}} > * {{CacheConfiguration.PluginConfigurations}} > * {{IPluginProvider}} > * {{ICachePluginProvider}} > * {{IPluginContext}} > * {{ICachePluginContext}} > Should work like this: > * Plugin author implements {{IPluginProvider}} > * We discover plugins on Ignite start by examining all DLL files in the > folder, load DLLs where {{IPluginProvider}} implementations are present, > instantiate these implementations, and call > {{IPluginProvider.Start(IPluginContext)}} method. > * Plugin user can retrieve plugin via {{IIgnite.GetPlugin<T>(string name)}}, > or via helper extension method provided by plugin author. > This task does not include the possibility to interact with Java from the > plugin code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)