axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From d..@apache.org
Subject cvs commit: xml-axis/java/docs developers-guide.html user-guide.html
Date Fri, 06 Sep 2002 16:18:27 GMT
dug         2002/09/06 09:18:27

  Modified:    java/docs developers-guide.html user-guide.html
  Log:
  add some docs about soapmonitor
  Submitted by:	 Brian Price (pricebe@us.ibm.com)
  
  Revision  Changes    Path
  1.27      +14 -0     xml-axis/java/docs/developers-guide.html
  
  Index: developers-guide.html
  ===================================================================
  RCS file: /home/cvs/xml-axis/java/docs/developers-guide.html,v
  retrieving revision 1.26
  retrieving revision 1.27
  diff -u -r1.26 -r1.27
  --- developers-guide.html	4 Sep 2002 22:47:03 -0000	1.26
  +++ developers-guide.html	6 Sep 2002 16:18:27 -0000	1.27
  @@ -820,6 +820,20 @@
   <code>tcpmon</code> is described in more detail in the
   <a href="user-guide.html#tcpmon">AXIS User's Guide</a>.
   
  +<h4>Using <code>SOAP Monitor</code> to Monitor Functional Tests.</h4>
  +<p>
  +If you are debugging code that is running as a web application using
  +a web application server (such as Tomcat) then you may also use the
  +SOAP Monitor utility to view the SOAP request and response messages.
  +<br>Start up the SOAP monitor utility by loading the SOAP monitor applet 
  +in your web browser window:
  +<blockquote><tt>http://localhost:&lt;port&gt;/axis/SOAPMonitor</tt></blockquote>.
  +As you run your tests, the SOAP messages should appear in the SOAP 
  +monitor window.
  +<p>
  +<code>SOAP Monitor</code> is described in more detail in the
  +<a href="user-guide.html#soapmon">AXIS User's Guide</a>.
  +
   <h4>Running a Single Functional Test</h4>
   In one window start the server:
   <br>
  
  
  
  1.68      +31 -1     xml-axis/java/docs/user-guide.html
  
  Index: user-guide.html
  ===================================================================
  RCS file: /home/cvs/xml-axis/java/docs/user-guide.html,v
  retrieving revision 1.67
  retrieving revision 1.68
  diff -u -r1.67 -r1.68
  --- user-guide.html	4 Sep 2002 22:47:03 -0000	1.67
  +++ user-guide.html	6 Sep 2002 16:18:27 -0000	1.68
  @@ -42,6 +42,7 @@
     </ul>
     <li> <a href="#published interfaces">Published Interfaces</a></li>
     <li> <a href="#tcpmon">Appendix : Using TCPMon</a></li>
  +  <li> <a href="#soapmon">Appendix : Using SOAP Monitor</a></li>
     <li> <a href="#Glossary">Glossary</a></li>
   </ul>
   
  @@ -228,7 +229,7 @@
   <p>The String argument is automatically serialized into XML, and the server
   responds with an identical String, which we deserialize and print.</p>
   <p><i>Note: to actually watch the XML flowing back and forth between a
  -SOAP client and server, you can use the included tcpmon tool. See the <a href="#tcpmon">appendix</a>
  +SOAP client and server, you can use the included <a href="#tcpmon">tcpmon</a>
tool or <a href="#soapmon">SOAP monitor</a> tool. See the appendix
   for an overview.</i></p>
   <h3>Naming Parameters</h3>
   In the above example, you can see that Axis automatically names the XML-encoded 
  @@ -1353,6 +1354,35 @@
     for testing the effects of different XML on SOAP servers. Note that you may 
     need to change the content-length HTTP header value before resending an edited 
     request. 
  +
  +<h2> <a NAME="soapmon"></a>Appendix: Using the SOAP Monitor </h2>
  +Web service developers often have the need to see the SOAP messages
  +being used to invoke web services along with the results of those
  +messages.  The goal of the SOAP Monitor utility is to provide 
  +a way for these developers to monitor the SOAP messages being used 
  +without requiring any special configuration or restarting of the 
  +server.
  +<p>
  +In this utility, a handler has been written and added to the global 
  +handler chain.  As SOAP requests and responses are received, the SOAP 
  +message information is forwarded to a SOAP monitor service where it 
  +can be displayed using a web browser interface.
  +<p>
  +The SOAP message information is accessed with a web browser by going
  +to http://localhost:&lt;port&gt;/axis/SOAPMonitor (where
  +&lt;port&gt; is the port number where the application server is
  +running).
  +<p>
  +The SOAP message information is displayed through a web browser
  +by using an applet that opens a socket connection to the SOAP
  +monitor service.  This applet requires a Java plug-in 1.3 or 
  +higher to be installed in your browser.  If you do not have a
  +correct plug-in, the browser should prompt you to install one.
  +<p>
  +The port used by the SOAP monitor service to comminicate with
  +applets is configurable.  Edit the web.xml file for the AXIS
  +web application to change the port to be used.
  +
   <a NAME="Glossary">
   <h2>Glossary</h2></a>
   
  
  
  

Mime
View raw message