[prev in list] [next in list] [prev in thread] [next in thread] 

List:       wss4j-dev
Subject:    [jira] [Created] (WSS-605) Ensure the ws-security-dom can work with the saaj impl in latest Java9 EA
From:       "Freeman Fang (JIRA)" <jira () apache ! org>
Date:       2017-03-31 7:30:41
Message-ID: JIRA.13060593.1490945406000.173248.1490945441761 () Atlassian ! JIRA
[Download RAW message or body]

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


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic