<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Further investigations seem to indicate that the SOAP server is
refusing the first connection attempt in any given startup. If this
expected? Since there are quite a few stop/starts happening as part of
the unit test suite, and since things like the methods in
SoapHttpClientTestCase only do one send per stop/start cycle, they are
coming back as false.<br>
<br>
Anyway, I've worked around around it for now by editing the class
method "start" in SoapServerSetup, so that after the handler is started
a temporary socket is created, connected to the handler's port (or not,
as the case may be :), then disconnected. After that all the unit tests
for the soap package that I was basing my code on pass! :)<br>
<br>
Sorry I can't help out more...<br>
S<br>
<br>
Simon Kirk wrote:
<blockquote cite="mid43E0A5CE.5070208@pinesoft.co.uk" type="cite">
<title></title>
Hi Masashi.<br>
<br>
No, this is on Squeak 3.8 (Smalltalk vmVersion returns 'Squeak3.8gamma
of ''24 November 2004'' [latest update: #6548]'), SUnit version 3.1.22,
SoapCore 0.8.<br>
<br>
It certainly seems like some kind of threading/timing issue - but
things are very strange. For a bit more detail: If I put a break point
in the method "testSimpleEnvelopeSend" in SoapHttpClientTestCase thus:<br>
<br>
<tt>testSimpleEnvelopeSend<br>
<br>
| curPort retXML envelope body method |<br>
SoapServerSetup startOnly: #(http).<br>
SoapServiceHandler default add: self simpleService.<br>
curPort := SoapSetting defaultPortAt: #http.<br>
self halt. ' <--------- Here's the break point<br>
retXML := (SoapHttpClient url: '<a class="moz-txt-link-freetext"
href="http://localhost:">http://localhost:</a>', curPort
printString, '/' ) send: self simpleEnvelope.<br>
envelope := SoapEnvelopeBuilder new buildSoapEnvelopeFromXmlString:
retXML.<br>
[snip]</tt><br>
<br>
Then if I wait a few seconds, the proceed, that test send works. If I
press process quickly, then it doesn't work.<br>
<br>
So it looks like the section where the <tt>simpleService</tt> is
added to the server isn't being given enough time to establish a
listening port. Does that look correct?<br>
<br>
Cheers,<br>
Simon<br>
<br>
Masashi UMEZAWA wrote:
<blockquote cite="mid98c242930602010324saa5266ct@mail.gmail.com"
type="cite">
<pre wrap="">Hi,
Do you use Squeak 3.9a? If so, I think it is partly because of the new
TestRunner, which seems to be running multi-threaded now.
I will upgrade my test cases for the next release.
Cheers,
2006/1/31, Simon Kirk <a class="moz-txt-link-rfc2396E"
href="mailto:Simon.Kirk@pinesoft.co.uk"><Simon.Kirk@pinesoft.co.uk></a>:
</pre>
<blockquote type="cite">
<pre wrap="">Hello all. I'm playing with the soap toolkit from SqueakMap, but
something seems to be wrong: If I run some SUnit tests (specifically
client ones - such as SoapHttpClientTestCase, or SoapCallTestCase) they
are failing, saying they cannot connect to the server (localhost, port
8823). However, if I step through the tests via debugging, right into
the point where the call is made to the server, the call appears to work
fine (a connection is made, the expected return is received).
What could be wrong here? It's almost like with the automated tests the
server is dying before the tests are ever connecting.
Cheers,
S
This message has been scanned for viruses by BlackSpider MailControl - <a
class="moz-txt-link-abbreviated" href="http://www.blackspider.com">www.blackspider.com</a>
</pre>
</blockquote>
<pre wrap=""><!---->
--
[:masashi | ^umezawa]
</pre>
</blockquote>
<br>
<br>
<font style="background-color: rgb(255, 255, 255);">
<p align="center"><font style="background-color: rgb(255, 255, 255);"
face="Tahoma" size="2">Click <a
href="https://www.mailcontrol.com/sr/wQw0zmjPoHdJTZGyOCrrhg==">here</a>
to report this email as spam.</font></p>
</font>
<pre wrap="">
<hr size="4" width="90%">
</pre>
</blockquote>
</body>
</html>