You can implement an alternative ResourceManagerCreator that does not set a new classloader and pass it to uimaFIT using ResourceManagerFactory.setResourceManagerCreator() before you run your application.
But why is the classloader that uimaFIT sets not adequate? For a bit of history on why this classloader is set, see: https://issues.apache.org/jira/browse/UIMA-3692 -- Richard On 25.08.2015, at 10:13, Peter Klügl <[email protected]> wrote: > Here's what happens: > > uimaFIT creates a new resource manager and sets the extension classpath, > which causes the creation of a new UIMAClassLoader. > > ResourceManager_impl.setExtensionClassPath(ClassLoader, String, boolean) > line: 229 > ResourceManagerFactory$DefaultResourceManagerCreator.newResourceManager() > line: > 62 > ResourceManagerFactory.newResourceManager() line: 42 > AnalysisEngineFactory.createEngine(AnalysisEngineDescription, Object...) > line: 205 > AnalysisEngineFactory.createEngine(Class<AnalysisComponent>, Object...) > line: 281 > StackedScriptsTest.test() line: 43 > > I am not yet sure how we can/should solve this problem... > > Best, > > Peter
