axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Glen Daniels <>
Subject RE: SOAPMonitor
Date Thu, 22 Aug 2002 16:50:27 GMT
Not at all, choice is a good thing.
However, the particular tool Doug is currently talking about is tightly integrated with Axis,
and doesn't require any host/port shuffling.

-----Original Message-----
From: Eoin Lane []
Sent: Thursday, August 22, 2002 11:27 AM
Subject: Re: SOAPMonitor

Sorry to chime in here but CapeScience ( <>
 ) the developers arm of  Cape Clear also have a free HTTP tool monitor call NetTool. It homepage
which includes a tutorial and download can be found at

Sorry to steal your thunder but then variety is the spices of life ;)


Doug Davis wrote:

Well its implemented using handlers (no changes to axis) so sure you can

deploy them just for certain services if you want - or on the global chain

(like we do for our demos).



                      Glen Daniels                                                       

                      <gdaniels@macrome        To:        "''" <mailto:''>
   <> <>     

            >                 cc:                                    

                                               Subject:  RE: SOAPMonitor                 

                      08/22/2002 10:22                                                   


                      Please respond to                                                  





Way cool.  Can you configure this on a per-service basis, or just at the

global level?



-----Original Message-----

From: Doug Davis [ <> ]

Sent: Thursday, August 22, 2002 10:20 AM

To: <> 

Subject: SOAPMonitor

In the latest version of IBM WSTK we've included a

SOAPMonitor tool.  This

tool is very much like TCPMon but it runs as an applet.  What

this means is

that, unlike TCPMon which works well for a single user looking at the

TCP/IP traffic on a port, SOAPMonitor allows multiple people

(on remote

hosts) to watch just the SOAP traffic going through an Axis

engine.  It

also does not require any changes to the client port #, or to

the server

port #.  It does require some handler deployment on the server since

they're the ones that send out the messages, but its a one time setup.

SOAPMonitor also allows you to filter messages based on the

service name.

Anyway, the reason I'm mentioning this is because we'd like

to know if you

guys would be interested in us contributing it to Axis.  Its

on alphaworks

( <>
) so

just let us know

- we find it useful for remote debugging and demos.






Eoin Lane PhD <> 


View raw message