You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ws.apache.org by "Freeman Fang (JIRA)" <ji...@apache.org> on 2017/03/31 07:30:41 UTC
[jira] [Created] (WSS-605) Ensure the ws-security-dom can work with
the saaj impl in latest Java9 EA kit
Freeman Fang created WSS-605:
--------------------------------
Summary: Ensure the ws-security-dom can work with the saaj impl in latest Java9 EA kit
Key: WSS-605
URL: https://issues.apache.org/jira/browse/WSS-605
Project: WSS4J
Issue Type: Improvement
Reporter: Freeman Fang
Assignee: Colm O hEigeartaigh
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 com.sun.org.apache.xerces.internal.dom.ElementNSImpl, 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
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org