[flexcoders] Re: WSDLError:Element not resolvable => LoadEvent doesn't imply service ready

2006-08-18 Thread ben.clinkinbeard
CTED] On > Behalf Of ben.clinkinbeard > Sent: Friday, August 18, 2006 10:24 AM > To: flexcoders@yahoogroups.com > Subject: [flexcoders] Re: WSDLError:Element not resolvable => LoadEvent > doesn't imply service ready > > > > Can we assume this will be corrected

[flexcoders] Re: WSDLError:Element not resolvable => LoadEvent doesn't imply service ready

2006-08-18 Thread ben.clinkinbeard
> > > > > > From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On > Behalf Of kaleb_pederson > Sent: Tuesday, August 15, 2006 12:28 PM > To: flexcoders@yahoogroups.com > Subject: [flexcoders] Re: WSDLError:Element not resolv

RE: [flexcoders] Re: WSDLError:Element not resolvable => LoadEvent doesn't imply service ready

2006-08-15 Thread Franck de Bruijn
> Seth > > > > > > From: [EMAIL PROTECTED]ups.com [mailto:[EMAIL PROTECTED]ups.com] On > Behalf Of kaleb_pederson > Sent: Tuesday, August 15, 2006 12:28 PM > To: [EMAIL PROTECTED]ups.com > Subject: [flexcoders] Re: WSDLError:Element

[flexcoders] Re: WSDLError:Element not resolvable => LoadEvent doesn't imply service ready

2006-08-15 Thread kaleb_pederson
t; From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] 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 >

RE: [flexcoders] Re: WSDLError:Element not resolvable => LoadEvent doesn't imply service ready

2006-08-15 Thread Seth Hodgson
[mailto:flexcoders@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 cop

[flexcoders] Re: WSDLError:Element not resolvable => LoadEvent doesn't imply service ready

2006-08-15 Thread kaleb_pederson
creating this WSDL I can try. Let me > know. > > > > Cheers, > > Franck > > > > _ > > From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On > Behalf Of Bill Sahlas > Sent: Wednesday, August 09, 2006 2:48 PM > To: flexcoder

RE: [flexcoders] Re: WSDLError:Element not resolvable => LoadEvent doesn't imply service ready

2006-08-15 Thread Franck de Bruijn
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

Re: [flexcoders] Re: WSDLError:Element not resolvable => LoadEvent doesn't imply service ready

2006-08-15 Thread Samuel D. Colak
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

RE: [flexcoders] Re: WSDLError:Element not resolvable => LoadEvent doesn't imply service ready

2006-08-15 Thread Bill Sahlas
: 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

RE: [flexcoders] Re: WSDLError:Element not resolvable => LoadEvent doesn't imply service ready

2006-08-08 Thread Franck de Bruijn
@yahoogroups.com [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

[flexcoders] Re: WSDLError:Element not resolvable => LoadEvent doesn't imply service ready

2006-08-08 Thread kaleb_pederson
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 p