I have created a Client Signing Handler to sign my SOAP envelopes with a digital signature when consuming a remote web service.
Like the Axis sample I broke this into two classes: - ClientSigningHandler - SignedSOAPEnvelope I created a ClientSigningHandler.wsdd (I removed the package name prefix for this email following the handler type...): <deployment xmlns="http://xml.apache.org/axis/wsdd/"; xmlns:java="http://xml.apache.org/axis/wsdd/providers/java";> <globalConfiguration> <requestFlow> <!-- define the client Signing handler configuration --> <handler type="java:ClientSigningHandler"> <parameter name="keystore" value="WEB-INF/keystore.jks"/> </handler> </requestFlow> </globalConfiguration> </deployment> I then registered my handler in the global configuration using the org.apache.axis.client.AdminClient tool. The problem is that the handler only seems to fire when I use the org.apache.axis.client.AdminClient tool to "list", not when my servlet makes my web service call. When I test my servlet I find that my web service call is made, but the ClientSigningHandler never seems to execute. The result is that the SOAP packet is sent, unsigned. As I said if I execute the "list" command from the AdminClient, I do see the ClientSigningHandler executing. I searched through the mailing list archives and found where somebody suggested checking for two files: - client-config.wsdd - server-config.wsdd It seems that only the 'server-config.wsdd' was created. I never received an error when executing the AdminClient tool, and it did appear to update the server-config.wsdd. Any suggestions? -- MM --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
