Functional tests broken?

[Glen Daniels <gd...@macromedia.com>]

I just tried running the functional tests and something weird is going on.  The mssoapinterop.org site seems to be down, which is timing out the WSDL2Java stuff.  For one thing, we're apparently bubbling up Exceptions about the connect timeout instead of printing the nice timeout message (only some of the time though!), and for another, the build just stops after the InteropC.wsdl timeout.  No "BUILD FAILED" message, nothing - just stops.

Russell, does this have to do with the revamped WSDL2Java (does it deal with timeouts differently?)?  Anyone else seeing this behaviour?

--Glen

Re: Functional tests broken?

[Steve Loughran <st...@iseran.com>]

----- Original Message -----
From: "Glen Daniels" <gd...@macromedia.com>
To: "Axis-Dev (E-mail)" <ax...@xml.apache.org>
Sent: Friday, May 10, 2002 6:15 AM
Subject: Functional tests broken?


>
> I just tried running the functional tests and something weird is going on.
The mssoapinterop.org site seems to be down, which is timing out the
WSDL2Java stuff.  For one thing, we're apparently bubbling up Exceptions
about the connect timeout instead of printing the nice timeout message (only
some of the time though!), and for another, the build just stops after the
InteropC.wsdl timeout.  No "BUILD FAILED" message, nothing - just stops.


ooh, that is usually caused by s System.exit() in a non-forked java app: set
fork=true, failonerror=true in your <java> call, and fork=true in junit to
avoid this

There is also a <condition> in ant1.5 that lets you probe for things being
reachable:

<condition property="interop.online">
 <http url="http://mssoapinterop.org"/>
</condition>


-steve