ting this WSDL I can try.
> Let me
> > know.
> >
> >
> >
> > Cheers,
> >
> > Franck
> >
> >
> >
> > _
> >
> > From: [EMAIL PROTECTED]ups.com
40yahoogroups.com>
>
> [mailto:[EMAIL PROTECTED]ups.com
40yahoogro
gt;
> Franck
>
>
>
> _
>
> From: [EMAIL PROTECTED]ups.com
[mailto:[EMAIL PROTECTED]ups.com]
On
> Behalf Of Bill Sahlas
> Sent: Wednesday, August 09, 2006 2:48 PM
> To: [EMAIL PROTECTED]ups.com
> Subject: RE: [flexcoders] Re: WSDLError:Element not resolvable
Sahlas
Sent: Wednesday, August 09, 2006
2:48 PM
To: flexcoders@yahoogroups.com
Subject: RE: [flexcoders] Re:
WSDLError:Element not resolvable => LoadEvent doesn't imply service ready
Howdy,
I’d like to reproduce this internally here in the FDS QA lab
using some of your
Title: Re: [flexcoders] Re: WSDLError:Element not resolvable => LoadEvent doesn't imply service ready
Hey Sahlas – actually the only test for a correctly loaded wsdl is the canLoadWSDL property. If this fails it is back to the drawing board.
As for a publicly accessible wsdl try m
: flexcoders@yahoogroups.com [mailto:flexcoders@yahoogroups.com] On Behalf Of Franck de Bruijn
Sent: Tuesday, August 08, 2006
1:59 PM
To: flexcoders@yahoogroups.com
Subject: RE: [flexcoders] Re:
WSDLError:Element not resolvable => LoadEvent doesn't imply service ready
Hi Kaleb,
Coo
Hi Kaleb,
Cool! Great stuff.
My guess is that the delay is machine
dependent, but not necessarily network dependent. I do believe that the LOAD
event does indicate that the WSDL actually has loaded successfully. Flex will
not need any more access to the network in order to initi
6 matches
Mail list logo
