-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
saaj-impl 1.5.3 regression with WS-Security and Apache Santuario #183
Comments
@lukasj, would be great if you could have look at this issue. In June we talked about it in eclipse-ee4j/metro-jax-ws#226 |
While testing with the changes of #173 I found the reason for this error and the fix is quite easy. Similar to
metro-saaj/saaj-ri/src/main/java/com/sun/xml/messaging/saaj/soap/impl/ElementImpl.java Lines 109 to 115 in f4dc3e3
So, this will fix the error. metro-saaj/saaj-ri/src/main/java/com/sun/xml/messaging/saaj/soap/impl/ElementImpl.java Lines 1676 to 1679 in f4dc3e3
@Override
public void setIdAttributeNode(Attr idAttr, boolean isId) throws DOMException {
- element.setIdAttributeNode(idAttr, isId);
+ if (idAttr instanceof AttrImpl) {
+ element.setIdAttributeNode(((AttrImpl)idAttr).delegate, isId);
+ } else {
+ element.setIdAttributeNode(idAttr, isId);
+ }
} |
This change fixes the delegation of setting the ID attribute node. fixes eclipse-ee4j#183 Signed-off-by: Ronny Perinke <[email protected]>
Signed-off-by: Ronny Perinke <[email protected]>
After updating to jaxws-rt 2.3.4 with saaj-impl 1.5.3 an exception occurs when validating incoming SOAP messages secured with ws-security using wssx-impl 2.4.5.
This as been also reported as SANTUARIO-570 and it might be related to #171.
How to reproduce
Please see the attached sample project. It contains a README how to reproduce the error.
metro-jax-ws-issue-226.zip
Exception
The text was updated successfully, but these errors were encountered: