I could have made this a reply on one of my previous posts but I think that this deserves a topic on its own.
I just want to hear from somebody who uses SOAPMonitor effectively. The reason is this - by analyzing the default axis web.xml, server-config.wsdd, SOAPMonitorApplet.java and Axis documentation I cannot see how that thing could possibly work.
One example - the applet reads a parameter named "port". Web xml calls that parameter "SOAPMonitorPort". Result - the port variable doesn't get initialized and applet cannot communcate with the server.
After I corrected that "small" bug, I got the SoapMonitor to "connect" with the server. The only problem is that it doesn't do anything. No SOAP monitoring of any kind, and (as far as I can see) no easyway of debugging the Axis classes that do the actual work.
What makes this all more misterious is the fact that a month ago I have set up and used SOAPMonitor without any problems. The only explanation I have is that maybe I had previous version of Axis that was bug free.
Can anybody put some light on this issue?
moose poop looks like football shaped elk poop. About the size of this tiny ad: