So I managed to get my client workimg by manually building and adding the soap header through my own SOAPHandler. What is so silly about all this is that the content of my header did not need to change beyond the value for the attribute "xmlns:wsse".
In other words, WSS4J does seem to support "http://schemas.xmlsoap.org/ws/2003/06/secext";, there is just know way to enable it. I believe the best way to resolve this would likely by on the server, by changing the security policy to accept "http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";, but in cases where this is not an option it would be nice to be able to change this manually on the client. dkulp wrote: > > > I don't think so. It LOOKS like that is kind of hard wired into WSS4J. > > Dan > > > On Mon June 22 2009 12:21:02 pm Acadaca wrote: >> Bump. >> >> To put the question another way- >> >> Can CXF support in wsse:Security >> http://schemas.xmlsoap.org/ws/2003/06/secext? Is there a way to override >> the dault which is >> xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecur >>ity-secext-1.0.xsd"? >> >> Thanks! > > -- > Daniel Kulp > [email protected] > http://www.dankulp.com/blog > > -- View this message in context: http://www.nabble.com/How-does-one-change-the-xmlns-on-a-Security-Header--tp24118201p24154188.html Sent from the cxf-user mailing list archive at Nabble.com.
