You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by Amit Pundir <am...@gmail.com> on 2017/11/08 20:03:48 UTC
Re: Ignite Plugin development ...
Hi,
I am writing a plugin and have followed the steps mentioned on this
conversation but the plugin is not discovered by Ignite node on start up.
I have created META-INF/services directories on my Ignite *server* node
under the 'libs' directory. I also tried keeping it at the same level as
'libs'.
I am using Ignite 2.0. Could you please tell me how you got it to work.
Thanks
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Ignite Plugin development ...
Posted by michal23849 <mi...@gmail.com>.
Hi, in this examples you have either WhiteListNullPlugin or
WhiteListAuthenticator
@Override
public IgnitePlugin plugin() {
System.out.println("****new plugin");
return new WhiteListNullPlugin();
}
@Override
public IgnitePlugin plugin() {
return new WhiteListAuthenticator();
}
Could you provide example implementation of this WhiteListHullPlugin /
WhiteListAuthenticator class?
Thanks
Michal
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Ignite Plugin development ...
Posted by myset <cr...@myset.ro>.
Previous example was done with 1.0 . It work also in 2.0.
Be aware of definition within
META-INF/services/org.apache.ignite.plugin.PluginProvider
and implementation itself.
Ex.
#SecurityPluginProvider comment line
ro.myset.appcore.grid.plugins.security.SecurityPluginProvider
Output log...
...
[09:43:43] VM information: Java(TM) SE Runtime Environment 1.8.0_112-b16
Oracle Corporation Java HotSpot(TM) 64-Bit Server VM 25.112-b16
[09:43:44] Configured plugins:
[09:43:44] ^-- SecurityPlugin 1.0
[09:43:44] ^-- MYSET SOLUTIONS S.R.L.
[09:43:44]
...
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/