Clay, I didn't quite understand your question fully. But if you are trying to add security header to the message you should use org.apache.ws.axis.security.WSDoAllSender and not org.apache.ws.axis.security.WSDoAllReceiver.
Sanjesh Real-Time Web Service Monitoring for Axis, Axis2 SoapKnox Inc http://www.soapknox.com Ph: 832 279 3745 -----Original Message----- From: Clay Dowling [mailto:[EMAIL PROTECTED] Sent: Monday, October 02, 2006 9:20 AM To: [email protected] Subject: WSDoAllReceiver: Request does not contain required Security header I'm getting this message back from my Axis 1.4 client that's using WSS4j 1.5.0 to handle the WS-Security encoding. My requestFlow section looks like this: <handler type="java:org.apache.ws.axis.security.WSDoAllReceiver"> <parameter name="passwordCallbackClass" value="ca.hcai.PWCallback" /> <parameter name="action" value="UsernameToken" /> <parameter name="user" value="signingcert" /> <parameter name="passwordType" value="PasswordText" /> </handler> There's nothing I could find in the documentation about manually adding a security header to the message. Am I missing something? Does anybody actually use WSS4J on this list, or is there a list that I would be better served to use? My last inquiry got no response at all, making me think that the tool isn't used in these parts. Clay --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
