For me, the advantage of SOAPMonitor over TcpMon is that you don't have to change the URL that the client connects to when using SOAPMonitor, it just sits in the normal handler chain and shows you the messages. With TcpMon, you have to make the client connect to a different endpoint. SOAPMonitor is also really nice if you have someone else connecting to your service and want to watch the messages, but the guy at the client end doesn't have to change anything.
My two cents. Dan Weston -----Original Message----- From: Zhaohua Meng [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 16, 2003 10:37 AM To: [EMAIL PROTECTED] Subject: Re: tcp and SOAP monitor Norris, I agree with you. I'm just curious. A technical person always tries to find an answer, although in most cases it's useless. Now I can use the tcpmon as a debugging tool which is all I need. Thank you very much for your response. Norris Merritt wrote: > Hi Zhaohua, I don't use SOAPMonitor. Not sure what the benefit is vs > tcpmon although I may be missing something. I think SOAPMonitor would > just annoy me because it does not show the HTTP headers. Without > those, you cannot see any SOAPAction header, which many (most? all?) > .NET services seem to want. > > -----Original Message----- > From: Zhaohua Meng [mailto:[EMAIL PROTECTED]] > Sent: Thursday, January 16, 2003 7:33 AM > To: Norris Merritt; [EMAIL PROTECTED] > Subject: Re: tcp and SOAP monitor > > > Norris, > > Thank you very much. I followed your instruction on tcpmon and it > worked!. But I'm greedy: in my situation, where client and service are > on the same host, how can I use SOAPMonitor? > > Thanks again. > Zhaohua > Norris Merritt wrote: > >>If your client and service are on the same host, you only need tcpmon. >>You have to arrange for your client to explicitly send the SOAP >>request to the host/port that tcpmon is listening on, and configure >>tcpmon to forward the SOAP request to the host/port that the web >>service is listening on. In > > other > >>words, tcpmon uses a man-in-the-middle strategy. >>-----Original Message----- >>From: Zhaohua Meng [mailto:[EMAIL PROTECTED]] >>Sent: Wednesday, January 15, 2003 4:17 PM >>To: [EMAIL PROTECTED] >>Subject: tcp and SOAP monitor >> >> >>Gurus, >> >>I'm a newbie here. I invoke the tcp and SOAP monitor as following >> >>java org.apache.axis.utils.tcpmon 10001 localhost 8080 >> >>http://localhost:8080/axis/SOAPMonitor >> >>When making a request to a service deployed successfully using command >>line, I can get the response back in the java console. However, nothing >>happens in the monitor screen except "Waiting for Connection..." >> >>I didn't change anything in the web.xml. >> >>Am I doing something wrong here? I'm using axis1.1beta. >> >>Thanks, >> >>Zhaohua Meng >> > > >
