You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-dev@ws.apache.org by Siddique Farhan-W13881 <fa...@motorola.com> on 2002/08/02 20:04:53 UTC
Displaying the SOAP Message before Call.invoke() and after succes
s
Hello,
How do i display SOAP messages before call.invoke and after success
to System.out..... Sample code would be very helpful. Thanks in advance
Regards,
Farhan
Re: Displaying the SOAP Message before Call.invoke() and after success
Posted by Scott Nichol <sn...@scottnichol.com>.
You cannot display the SOAP envelope before Call#invoke, because that is
when the marshalling occurs.
The best way to monitor what is being sent is using TcpTunnelGui included
with Apache SOAP, some other proxy or a network monitor. If you have access
to a UNIX-style platform, tcpdump is a great tool to use, as it is
completely non-invasive. Windows 2000 includes the Network Monitor
application to watch traffic in and out of the local machine.
To use TcpTunnelGui, you first run it like
java org.apache.soap.util.net.TcpTunnelGui 81 localhost 8080
The first argument is the port on which TcpTunnelGui listens. The second is
the host to which to forward connections. The third is the port on that
host to connect to. The example above makes TcpTunnelGui listen on port 81
and forward to localhost:8080, which is where Tomcat is listening on my
machine.
With TcpTunnelGui (and other proxies), you make it the endpoint URL for your
SOAP calls. With the app running as above, I could run the following
java samples.addressbook.GetAddress
http://localhost:81/soap/servlet/rpcrouter "John Doe"
My SOAP client connects to TcpTunnelGui, which will forward to Tomcat.
Scott Nichol
----- Original Message -----
From: "Siddique Farhan-W13881" <fa...@motorola.com>
To: <so...@xml.apache.org>
Sent: Friday, August 02, 2002 2:04 PM
Subject: Displaying the SOAP Message before Call.invoke() and after success
Hello,
How do i display SOAP messages before call.invoke and after success
to System.out..... Sample code would be very helpful. Thanks in advance
Regards,
Farhan
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
Re: Displaying the SOAP Message before Call.invoke() and after success
Posted by Scott Nichol <sn...@scottnichol.com>.
You cannot display the SOAP envelope before Call#invoke, because that is
when the marshalling occurs.
The best way to monitor what is being sent is using TcpTunnelGui included
with Apache SOAP, some other proxy or a network monitor. If you have access
to a UNIX-style platform, tcpdump is a great tool to use, as it is
completely non-invasive. Windows 2000 includes the Network Monitor
application to watch traffic in and out of the local machine.
To use TcpTunnelGui, you first run it like
java org.apache.soap.util.net.TcpTunnelGui 81 localhost 8080
The first argument is the port on which TcpTunnelGui listens. The second is
the host to which to forward connections. The third is the port on that
host to connect to. The example above makes TcpTunnelGui listen on port 81
and forward to localhost:8080, which is where Tomcat is listening on my
machine.
With TcpTunnelGui (and other proxies), you make it the endpoint URL for your
SOAP calls. With the app running as above, I could run the following
java samples.addressbook.GetAddress
http://localhost:81/soap/servlet/rpcrouter "John Doe"
My SOAP client connects to TcpTunnelGui, which will forward to Tomcat.
Scott Nichol
----- Original Message -----
From: "Siddique Farhan-W13881" <fa...@motorola.com>
To: <so...@xml.apache.org>
Sent: Friday, August 02, 2002 2:04 PM
Subject: Displaying the SOAP Message before Call.invoke() and after success
Hello,
How do i display SOAP messages before call.invoke and after success
to System.out..... Sample code would be very helpful. Thanks in advance
Regards,
Farhan
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>