ws-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Veithen (JIRA)" <>
Subject [jira] [Commented] (WSS-605) Ensure the ws-security-dom can work with the saaj impl in latest Java9 EA kit
Date Wed, 05 Apr 2017 20:36:41 GMT


Andreas Veithen commented on WSS-605:

A couple of comments here:

* The patch doesn't contain any test cases that demonstrate the problem (The current trunk
just builds fine with Java 9).
* I'm missing a clear explanation of the problem. In particular, is the problem that WSS4J
makes assumptions about DOM or SAAJ that are incorrect, or is the problem that Java 9 no longer
conforms to these specs and we are trying to work around that?
* The patch makes an incorrect assumption, namely that any software running on Java 9 would
necessarily use the SAAJ implementation provided by the JRE.

> Ensure the ws-security-dom can work with the saaj impl in latest Java9 EA kit
> -----------------------------------------------------------------------------
>                 Key: WSS-605
>                 URL:
>             Project: WSS4J
>          Issue Type: Improvement
>            Reporter: Freeman Fang
>            Assignee: Colm O hEigeartaigh
>             Fix For: 2.2.0
>         Attachments: WSS-605-new2.patch, WSS-605-new3.patch, WSS-605-new.patch, WSS-605.patch
> In latest JDK9 EA kit, the SAAJ api changed, for example, the
> com.sun.xml.internal.messaging.saaj.soap.impl.ElementImpl now not extends its dom counterpart, instead it store it as a field and add
a method
> {code}
>     public Element getDomElement() {
>         return element;
>     }
> {code}
> to get it. so the extends become aggregates.
> This change cause lots of ClassCastException and wrong DocOwner exception which use ws-seucrity-dom
which rely on the Dom and Saaj api heavily.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message