zzh
/
gatk-3.8
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Added verbose error message to the PluginManager 

-- added a logger.error with a more descriptive message of what the most likely cause of the error is

Typical error happens when a walker's global variable is not initialized properly (usually in test conditions). The old error message was very hard to understand "Could not create module because of an exception of type NullPointerException ocurred caused by exception null"
This commit is contained in:
Mauricio Carneiro 2013-02-18 11:11:18 -05:00
parent 8eda0c50df
commit 815028edd4
1 changed files with 5 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
public/java/src/org/broadinstitute/sting/utils/classloader/PluginManager.java
View File

@ -25,6 +25,8 @@
package org.broadinstitute.sting.utils.classloader;
import org.apache.log4j.Level;
import org.apache.log4j.Logger;
import org.broadinstitute.sting.gatk.WalkerManager;
import org.broadinstitute.sting.gatk.filters.FilterManager;
import org.broadinstitute.sting.utils.exceptions.DynamicClassResolutionException;
@ -299,11 +301,14 @@ public class PluginManager<PluginType> {
* @return The plugin object if created; null otherwise.
*/
public PluginType createByType(Class<? extends PluginType> pluginType) {
Logger logger = Logger.getLogger(PluginManager.class);
logger.setLevel(Level.ERROR);
try {
Constructor<? extends PluginType> noArgsConstructor = pluginType.getDeclaredConstructor((Class[])null);
noArgsConstructor.setAccessible(true);
return noArgsConstructor.newInstance();
} catch (Exception e) {
logger.error("Couldn't initialize the plugin. Typically this is because of wrong global class variable initializations.");
throw new DynamicClassResolutionException(pluginType, e);
}
}