[
https://issues.apache.org/jira/browse/WSS-605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15957142#comment-15957142
]
Colm O hEigeartaigh commented on WSS-605:
-----------------------------------------
Hi [~ffang],
Would it work to replace the following line:
header = createElementInSameNamespace(((SOAPPart)doc).getEnvelope(),
WSConstants.ELEM_HEADER);
with:
header = createElementInSameNamespace(doc.getDocumentElement(),
WSConstants.ELEM_HEADER);
? The former causes errors when using JDK9 to run the ws-security-dom tests due
to a missing dependency on javax.xml.soap. I know we can fix the test setup to
add the module etc. but the latter is an easier fix if it works?
Colm.
> 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
> 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 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: [email protected]
For additional commands, e-mail: [email protected]
