DO NOT REPLY [Bug 20679] - SOAPMonitorApplet source/class file missing

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20679>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20679

SOAPMonitorApplet source/class file missing





------- Additional Comments From petter.mahlen@chello.se  2003-06-11 14:37 -------
Have spent some more time on it, and the source code is stored directly under 
the webapps/axis directory of the distribution. However, it is not easy to find 
out how to use it. I would suggest adding something like this (only improved) 
to the user's guide:


To use the SOAPMonitor, you need to perform the following steps:
1. Compile and make available the applet that is the client GUI for the monitor.
2. Configure the Axis server to notify the monitor of requests for the relevant 
services.
3. Configure the Axis server to notify the monitor of responses for the 
relevant services.

Step 1 is easy, assuming you have a working Axis installation: just 'cd' to the 
webapps/axis directory of the servlet container ($CATALINA_HOME/webapps/axis 
for Tomcat), and execute the command "javac -classpath 
AXISINSTALLDIR/lib/axis.jar SOAPMonitorApplet.java". This compiles the applet 
and its nested classes, and makes them available to the servlet container.

Step 2 is a little more complicated. For each service that should be monitored, 
you need to set up a request flow that calls the SOAPMonitor. This means that 
you need to add the following to the WSDD file that you use to deploy services:

<deployment xmlns="http://xml.apache.org/axis/wsdd/"
            xmlns:java="http://xml.apache.org/axis/wsdd/providers/java">
 <handler name="monitor" 
type="java:org.apache.axis.handlers.SOAPMonitorHandler">
 </handler>

 .. mappings and other things

 <service name="MyService" provider="java:RPC">
  <requestFlow>
    <handler type="monitor"/>
  </requestFlow>
  <parameter name="className" value="com.company.package.MyService"/>
  <parameter name="allowedMethods" value="*"/>
 </service>
</deployment>

That is, first define the monitoring handler, and then ensure that for each 
service you want to monitor, the monitoring handler will be called before the 
service is invoked.

Step 3 - I haven't succeeded with this one yet, someone there who can help?