ws-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Colm O hEigeartaigh (JIRA)" <>
Subject [jira] [Closed] (WSS-439) Error in using StaX WS-Security + CXF WS-Addressing
Date Tue, 06 May 2014 09:11:22 GMT


Colm O hEigeartaigh closed WSS-439.

> Error in using StaX WS-Security + CXF WS-Addressing
> ---------------------------------------------------
>                 Key: WSS-439
>                 URL:
>             Project: WSS4J
>          Issue Type: Bug
>            Reporter: Karm Hoan
>            Assignee: Marc Giger
>             Fix For: 2.0.0
> There is an error when using WSS4J's StaX functionality with CXF with WS-Addressing enabled.
I've created the following demo for streaming signature + encryption in CXF, based on the
DOM demo:
> This demo can be run via "mvn -Pserver" and "mvn -Pclient". It works perfectly without
WS-Addressing. Now edit the following files + uncomment the addressing feature:
> The client produces the following SOAP Header fragment:
> <soap:Header><Action xmlns=""></Action><MessageID>urn:uuid:d7ca1c25-52da-447b-963b-f3d8e498f591</MessageID><To>http://localhost:9000/SoapContext/GreeterPort</To><ReplyTo><Address>http://localhost:9990/decoupled_endpoint</Address></ReplyTo><wsse:Security
> As you can see, the "Action" header is in the correct namespace. However, the subsequent
WS-A headers are not. Dan reckons there is confusion in the namespace stack, where perhaps
the namespace stack is not being popped on the endElement of "Action",
> For the record, the server complains with:
> org.apache.cxf.binding.soap.SoapFault: A required header representing a Message Addressing
Property is not present
> 	at

This message was sent by Atlassian JIRA

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

View raw message