Due to recent updates, all users are required to create an Altair One account to login to the RapidMiner community. Click the Register button to create your account using the same email that you have previously used to login to the RapidMiner community. This will ensure that any previously created content will be synced to your Altair One account. Once you login, you will be asked to provide a username that identifies you to other Community users. Email us at Community with questions.
NullPointerException with selfmade Plugin
Hi!
I've found another small bug. In a plugin manifest you can name an PluginInit-class (see whitepaper). If you don't do this rapidminer hangs with an NullPointerException. The reason is in [tt]Plugin.showAboutBox[/tt] (as of 5.0.006):
As workaround till the next update just use an initialisation class with empty methods.
Best regards,
chero
I've found another small bug. In a plugin manifest you can name an PluginInit-class (see whitepaper). If you don't do this rapidminer hangs with an NullPointerException. The reason is in [tt]Plugin.showAboutBox[/tt] (as of 5.0.006):
public boolean showAboutBox() {The problem is pluginInitClassName. If you don't supply a name for the plugin init class this variable is [tt]null[/tt] and [tt]Class.forName[/tt] issues a NullPointerException. Though you catch many exception types you forgot this one
try {
Class<?> pluginInitator = Class.forName(pluginInitClassName, false, getOriginalClassLoader());
Method initGuiMethod = pluginInitator.getMethod("showAboutBox", new Class[] {});
Boolean showAboutBox = (Boolean) initGuiMethod.invoke(null, new Object[] {});
return showAboutBox.booleanValue();
} catch (ClassNotFoundException e) {
} catch (SecurityException e) {
} catch (NoSuchMethodException e) {
} catch (IllegalArgumentException e) {
} catch (IllegalAccessException e) {
} catch (InvocationTargetException e) {
}
return true;
}
As workaround till the next update just use an initialisation class with empty methods.
Best regards,
chero
Tagged:
0
Answers
thanks for reporting this. It is fixed.
Cheers,
Simon