Of kaleb_pederson
Sent: Tuesday, August 15, 2006 12:28 PM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] Re: WSDLError:Element not resolvable = LoadEvent
doesn't imply service ready
Hello all,
I have provided Bill at Adobe with a copy of the WSDL and XSD for
the test service
@yahoogroups.com
Subject: [flexcoders] Re: WSDLError:Element not resolvable = LoadEvent
doesn't imply service ready
Can we assume this will be corrected in a future release? Either by
changing when the LoadEvent fires or by adding a separate event to
listen for?
Thanks,
Ben
@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,
Cool! Great stuff
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 my server
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,
Id like to reproduce this internally here in the FDS QA lab
using some of your examples. Can
_
From: flexcoders@yahoogroups.com
[mailto:[EMAIL PROTECTED] On
Behalf Of Bill 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
@yahoogroups.com] On Behalf Of kaleb_pederson
Sent: Tuesday, August 15, 2006
12:28 PM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] Re:
WSDLError:Element not resolvable = LoadEvent doesn't imply service ready
Hello all,
I have provided Bill at Adobe with a copy of the WSDL and XSD
To: flexcoders@yahoogroups.com
Subject: [flexcoders] Re: WSDLError:Element not resolvable =
LoadEvent
doesn't imply service ready
Hello all,
I have provided Bill at Adobe with a copy of the WSDL and XSD for
the test service. I haven't received a response but assume that he
received
]
On
Behalf Of kaleb_pederson
Sent: Tuesday, August 15, 2006 12:28 PM
To: [EMAIL PROTECTED]ups.com
Subject: [flexcoders] Re: WSDLError:Element not resolvable =
LoadEvent
doesn't imply service ready
Hello all,
I have provided Bill at Adobe with a copy of the WSDL and XSD for
the test service
[mailto:flexcoders@yahoogroups.com] On Behalf Of kaleb_pederson
Sent: Tuesday, August 08, 2006
7:18 PM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] Re:
WSDLError:Element not resolvable = LoadEvent doesn't imply service ready
Frank,
I did a bit more research into this. I don't
Frank,
I did a bit more research into this. I don't need nearly a second
for the WebService to be ready after the load event. I just put the
whole process in a loop to see what kind of delay I need to make it
work on my box (with the service running on my box). Unfortunately,
the delay is
11 matches
Mail list logo
