[
https://issues.jboss.org/browse/JBWS-4160?page=com.atlassian.jira.plugin....
]
Jan Blizňák commented on JBWS-4160:
-----------------------------------
Because I wasn't able to find the difference on JBossWS/CXF side I started to dig
deeper on JDK side. I was able to locate the place after which RHEL execution continues
without error but Win execution reports some number of errors (log.nerrors counter > 0)
at
http://hg.openjdk.java.net/jdk/jdk11/file/jdk-11+28/src/jdk.compiler/shar...
I was not able to find the root cause at alocated time, but still I would say the problem
comes probably sooner on JBossWS/CXF side and I missed it somewhere.
Also there might be problem with the test as it is rather complicated scenario and all
other tests with ws-provide* and ws-consume* stuff works on all OS/JVM...
Test failure of WSProviderTestCaseForked on JDK11+Windows
---------------------------------------------------------
Key: JBWS-4160
URL:
https://issues.jboss.org/browse/JBWS-4160
Project: JBoss Web Services
Issue Type: Bug
Components: jbossws-cxf
Affects Versions: jbossws-cxf-5.2.4.Final
Reporter: Jan Blizňák
Priority: Major
We are seeing failing test
org.jboss.test.ws.jaxws.smoke.tools.WSProviderTestCaseForked#testOutputDirectory
https://github.com/jbossws/jbossws-cxf/blob/jbossws-cxf-5.2.4.Final/modul...
The error message is:
{code:java}
java.lang.reflect.InvocationTargetException
at
org.jboss.test.ws.jaxws.smoke.tools.WSProviderTestCaseForked.testOutputDirectory(WSProviderTestCaseForked.java:105)
Caused by: java.lang.ClassNotFoundException:
org.jboss.test.ws.jaxws.smoke.tools.jaxws.AddResponse
at
org.jboss.test.ws.jaxws.smoke.tools.WSProviderTestCaseForked.testOutputDirectory(WSProviderTestCaseForked.java:105)
{code}
During the test this is called
https://github.com/jbossws/jbossws-cxf/blob/jbossws-cxf-5.2.4.Final/modul...
after which "target/wsprovide/java/org/jboss/test/ws/jaxws/smoke/tools/jaxws/"
should contain both *.java and *.class files but it does not on Win+JDK11. The cause of
the test error message is then the fact there are no *.class files in tested directory.
In case of JDK11 the Jdk9PlusJBossModulesAwareCompiler is used which then calls JDK
internal compiler task
https://github.com/jbossws/jbossws-cxf/blob/jbossws-cxf-5.2.4.Final/modul...
which should create these files.
When I was trying to debug it on both Win and RHEL with JDK11 and compare results, there
seems to be no relevant difference at what parameters are passed to methods up to this
point.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)