On Tuesday 07 October 2008 5:11:05 pm jmdev wrote: > My current project requires the use of 3rd party Axis 1.* handlers to > format a SOAP message. One of the handlers is a custom digital signature > handler which digitally signs selective parts of the message. I have > successfully called the handler from a CXF SOAPHandler. The problem is > that the subsequent conversion of the SoapMessage to a stream using StAX is > invalidating the digital signatures since the message is "rebuilt". > > Would it be possible to send the SOAPMessage from the handlers as-is > without processing by the StAX based interceptors? If so, what would I > need to do to accomplish this?
Honestly, I don't think there is a way to do it now. However, I'm trying to see why it would impact this. Our own WS-Security interceptors do the same thing digitally signing particular elements and such and it doesn't have any problem going through the stax stuff at all. If the signing and verification is done on canonicalized form of the XML like the specs say it should be, then it shouldn't matter. Basically, I'd like to know what the stax stuff is doing that would cause the signatures to be "different". -- Daniel Kulp [EMAIL PROTECTED] http://dankulp.com/blog
