I've not had "not resolvable" issues, but I did have some other significant issues with namespaces in .NET web services, especially default namespaces. I documented my solutions on my site.
http://www.returnundefined.com/2006/07/dealing-with-default-namespaces-in-flex-2as3/ http://www.returnundefined.com/2006/07/datagrid-labelfunction-and-namespaces/ HTH, Ben --- In flexcoders@yahoogroups.com, "Tom Lee" <[EMAIL PROTECTED]> wrote: > > Exactly what I was looking for, James! Thanks so much... The request was > not being sent at all, so I stepped into the debugger. It turns out I have > a WSDL error - looks like the WSDLParser is choking on a namespace, saying > it's "not resolvable". It's one of those ASP.Net default "tempuri.org" > namespaces. Anyone ever have trouble with ASP.Net web service namespaces? > > -----Original Message----- > From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On > Behalf Of james_dhap > Sent: Thursday, August 10, 2006 3:27 PM > To: flexcoders@yahoogroups.com > Subject: [flexcoders] Re: Debugging Web Service call > > Hi Tom, > There are two places I would recommend starting with. The first is to > see if any data is actually being sent out by the player to the > WebService. The easiest way to do this is to use an HTTP request > debugger to sniff the outgoing/incoming data. There are a lot of > options out there but I prefer Tamper Data (see my previous post), > mainly because it intergrates with Firefox: > > https://addons.mozilla.org/firefox/966/ > > What you want to do with this app (or any other debugger) is to see if > the request is being sent out to the service by the player. If you > don't see a request being sent out then you know that there is some > problem in your Flex code or a conflict in the Flex Framework. If the > data never leaves I would set a breakpoint on the send method and > start stepping into the Framework code and see where it goes wrong. > > If you see the request is being sent but nothing is being returned > then you can pursue the service and verify that its not hanging or > doing something wrong. > > It's kind of hard to recommend other ideas without seeing your code, > but I totally understand why you can't post it. > > -- James > > > --- In flexcoders@yahoogroups.com, "Tom Lee" <design@> wrote: > > > > Yeah, I hate generic questions too, sorry about that. Problem is, I > can't > > show you the web services due to company policy, and can't show you > my code > > because it would expose the web services. I can tell you that I've > > connected successfully to other web services using the same syntax, > so I'm > > pretty sure my code's not at fault. > > > > What I'm really after are general tips on debugging web service calls. > > Usually you'd look at the fault message when a call fails, but this > failure > > isn't generating a fault. Also, it prevents subsequent function > calls from > > executing, which I find odd: > > > > function doIt():void{ > > myWebService.myMethod.send(); > > //The following will not fire: > > Alert.show("Call made to webservice"); > > } > > > > Sorry I can't post my code. I appreciate anything you might be able to > > offer despite that fact. > > > > -tom > > > > -----Original Message----- > > From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On > > Behalf Of flexnadobe > > Sent: Thursday, August 10, 2006 12:29 PM > > To: flexcoders@yahoogroups.com > > Subject: [flexcoders] Re: Debugging Web Service call > > > > Hi Tom, > > > > If you want try to post some code so we can see what you are doing? > > There are alot of cool bro's on this site that will help but we will > > need a starting point. > > > > cya, > > > > Rich > > > > --- In flexcoders@yahoogroups.com, "Tom Lee" <design@> wrote: > > > > > > Hi guys, > > > > > > > > > > > > I'm having some trouble with a WebService call and can't seem to > > pinpoint > > > the trouble. The WSDL loads fine, but any calls to the web service > > result > > > in nothing. No fault, no result, not even the busy cursor (even > > though I've > > > got showBusyCursor="true"). Anyone have any suggestions for how I > might > > > debug this? Are there any low-level status events I can hook into? > > > > > > > > > > > > I have better luck with the MXNA web services, so I know my syntax > > is right. > > > > > > > > > > > > Thanks! > > > > > > > > > > > > -tom > > > > > > > > > > > > > > > > > > > -- > > Flexcoders Mailing List > > FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt > > Search Archives: > http://www.mail-archive.com/flexcoders%40yahoogroups.com > > Yahoo! Groups Links > > > > > > > > > -- > Flexcoders Mailing List > FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt > Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com > Yahoo! Groups Links > -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
