Date: Wed, 30 Nov 2005 23:27:48 +0800
From: Cara MacNish <email@hidden>
Subject: TCPMonitor shows initial wsdl lookup but not invoke calls
To: email@hidden
Message-ID: <email@hidden>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Hi, I have a basic web service example working and am trying to use
TCPMonitor to view the SOAP messages for the method invocations. With
the help of a googled websphere document (the apple doc only gives
instuctions for using it with D2WS and makes no sense otherwise) I
worked out how it works. Its now catching messages that appear to
contain the whole wsdl spec of all the methods and data types, but I
cannot get it to catch an invoke call - ie the SOAP package of an
actual method invocation - despite the fact that the methods are
working fine.
The only conjecture I can think of is that, while I point the client
to the TCPMonitor listen port, when it first looks up the wsdl, it
passes through the TCPMonitor (the message I get) but that then
rather than using the port I've pointed it to (the listen port) for
subsequent requests, it gets the port published in the wsdl and uses
that for all subsequent requests, thus bypassing the monitor. Does
that make sense? If so, then I could get around this if I edited the
wsdl, but I assume this only exists "in the server's memory" as I
can't find any file for it.
Am I missing something?
Cheers
Cara
ps. Thanks for the humour Wolfram :)