You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Richard Eckart de Castilho (Jira)" <de...@uima.apache.org> on 2021/07/09 14:58:00 UTC
[jira] [Updated] (UIMA-6379) Drop uimaj-adapter-soap due to Java 16
issues in Eclipse
[ https://issues.apache.org/jira/browse/UIMA-6379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Richard Eckart de Castilho updated UIMA-6379:
---------------------------------------------
Summary: Drop uimaj-adapter-soap due to Java 16 issues in Eclipse (was: Drop uimaj-adapter-soap due to Java 16 issues)
> Drop uimaj-adapter-soap due to Java 16 issues in Eclipse
> --------------------------------------------------------
>
> Key: UIMA-6379
> URL: https://issues.apache.org/jira/browse/UIMA-6379
> Project: UIMA
> Issue Type: Bug
> Components: Transport Adapters - SOAP, Vinci
> Reporter: Richard Eckart de Castilho
> Priority: Major
>
> uimaj-adapter-soap does not build in Eclipse against Java 16.
> When changing the Java source/target level in Maven Build from 1.8 to 16, the uimaj-adapter-soap displays errors: "QName cannot be resolved to a type".
> The reason for this is that the module has multiple dependencies including the JDK itself which provides this class and in Java Modules, a package must be exclusive to a certain module.
> In particular, the module depends on Apache Axis JAX-RPC which contains {{javax.xml.namespace.QName}}.
> I wonder if the SOAP module is actually still used by anybody - I'd personally tend towards dropping it.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)