Open matejsp opened 6 years ago
Hello Guys,
Any update about this issue ?
JDK bug for tracking the same issue: https://bugs.openjdk.java.net/browse/JDK-8196491
Yes, at the moment i have disable my saop handlers...
JDK-8196491 bug has been resolved in jdk8u-dev. Standalone fixes for JAXWS-RI and JAXB-RI have been delivered through these changesets: JAXWS-RI part: https://github.com/javaee/metro-jax-ws/commit/5a06cb2d0b5ef884cc87ef431e7add458322aab8 JAXB-RI part: https://github.com/javaee/jaxb-v2/commit/8f1e74a7d3439d7f4c3f07689337c00d9e915628
I guess that this issue can be closed now
Fix is expected to be included in Version 8u192. Expected release date : October 2018
So no progression beyond 8u151, unless they backport it
I see this with standalone JAX-WS RI 2.3.0 as downloaded via Maven and JDK9 (eg zulu9.0.7.1-jdk9.0.7-win_x64). My codebase now relies on Java9 features and I can't move it back.
So: is this fix slated to be released in a (still useable from jdk9) JAX-WS RI 2.3.1 any time soon?
BTW: I tried compiling my own release locally but failed pretty miserably (undefined references to com.sun...internal classes, for example; couldn't find any build instructions anywhere...)
I'm looking to having to sanitise all my data manually (field-by-field) and this 'solution' is rather unappealing...
@transentia can you post how you were able to pull in JAX-WS as a maven dependency?
I'm pulling in dependencies from mavenCentral in Gradle:
repositories {
mavenCentral()
}
…
// https://mvnrepository.com/artifact/javax.xml.ws/jaxws-api
implementation group: 'javax.xml.ws', name: 'jaxws-api', version: '2.3.0'
implementation 'org.jvnet.jax-ws-commons.spring:jaxws-spring:1.9'
// https://mvnrepository.com/artifact/com.sun.xml.ws/jaxws-rt
implementation group: 'com.sun.xml.ws', name: 'jaxws-rt', version: '2.3.0', ext: 'pom'
it's fixed on the 1_8_172 (check release note here : http://www.oracle.com/technetwork/java/javaseproducts/documentation/8u172-revision-builds-relnotes-4465508.html )
Thanks for that.
Is there a timeline for the standalone release? As I said, I have moved to JDK 9 features and can't go back, so the standalone is the only option for me...
There is a new regression based on the latest release of JDK. I have reproduced the problem using non JDK version of JAX-WS (version 2.3.0:
The problem visible only when using combination of client WS and SoapHandler. It fails with message "Entity References are not allowed in SOAP documents" where the reference is "#xd" inside createEntityReference method call. It seems that new lines are now escaped (#xd or #0a). And this seems to bug createEntityReference logic.
Example:
Stacktrace: