Re: TCPMonitor shows initial wsdl lookup but not invoke calls

Thu, 01 Dec 2005 14:41:53 -0800

there are a few strategies for dealing with this.  Partially it depends on if the server and client are on the same machine for development.

if client and server on same machine:
what I do is let the client connect to the server and get the wsdl.  Now the client knows where the server is and what port to talk to.  Now shut down the server and move it over a few port numbers and start up TCPMonitor to listen on the original server port and output to the new port.

if the server is on a different machine:
in this case I usually grab the wsdl by hitting the server's wsdl url in a browser and viewing the source.  Then I save it to a file and change all servername:port references to 127.0.0.1:port num with the port number being the port number I am starting TCPMonitor listening on.

On another subject, if you need to customize your WSDL to be compatible with non-Apple clients, consider going the D2WS route with frozen components...

Alex

__alex cone
        ceo  c o d e f a b  inc
        [EMAIL PROTECTED]
        212.465.8484 x101

"New Orleans food is as delicious as the less criminal forms of sin." ---Mark Twain, 1884

On Nov 30, 2005, at 12:54 PM, [EMAIL PROTECTED] wrote:

Date: Wed, 30 Nov 2005 23:27:48 +0800

From: Cara MacNish <[EMAIL PROTECTED]>

Subject: TCPMonitor shows initial wsdl lookup but not invoke calls

To: [email protected]

Message-ID: <[EMAIL PROTECTED]>

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 :)



 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to