You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Marshall Schor (JIRA)" <de...@uima.apache.org> on 2018/11/19 16:15:00 UTC

[jira] [Resolved] (UIMA-5907) uima-as dd2spring fails due to classloading setup, after UIMA-5754

     [ https://issues.apache.org/jira/browse/UIMA-5907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marshall Schor resolved UIMA-5907.
----------------------------------
    Resolution: Fixed

> uima-as dd2spring fails due to classloading setup, after UIMA-5754
> ------------------------------------------------------------------
>
>                 Key: UIMA-5907
>                 URL: https://issues.apache.org/jira/browse/UIMA-5907
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>    Affects Versions: 2.10.3AS
>            Reporter: Marshall Schor
>            Assignee: Marshall Schor
>            Priority: Major
>             Fix For: 2.10.4AS
>
>
> UIMA-5754 changed how the bootstrap class loader sets up class path, because after Java 9, it is no longer possible to add classes to the application classpath.  This change breaks how dd2spring sets up the classpath for saxon.  It needs to set this up with a special extra class loader which implements the logic of trying the thread-local context class loader, but if a resource is not found there, then trying the classloader used to load the uima classes (which is no longer the application class loader, which is the value of the ThreadLocal context ClassLoader. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)