Well, I figured it out. I'm fairly new to Flex so please hold your laughter. 
What happened is that I was calling 3 HTTPService requests to the database and 
then calling an internal function to work with the data I had received. What I 
didn't realize was that Flex makes those calls asynchronously (I know, I know - 
stop laughing).

So, I was hitting an error in my internal function because it was trying to 
work with an XMLListCollection that hadn't been populated yet (it was null). I 
would put a breakpoint in my result function, but of course, the Flex app had 
already tripped up before the results were returned.

So now I'm "daisy-chaining" my HTTPServices so that the 2nd one is called from 
within the 1st calls result function. And the 3rd within the 2nd, and then 
finally calling my internal function from within the 3rd result function...if 
that makes any sense.

Anyway, thanks for everyone's help. Have a great day!

--- In [email protected], "valdhor" <valdhorli...@...> wrote:
>
> Have you set up another event listener (using Actionscript) that is grabbing 
> that event?
> 
> 
> --- In [email protected], "Matthew A. Wilson" <korband@> wrote:
> >
> > I have a component that I'm adding to my Flex project and it makes 3 HTTP 
> > Service calls. On the result="" I have listed a function and inside that 
> > function I have created a breakpoint.
> > 
> > When I go into debug, it won't stop at that breakpoint. It's like it's not 
> > calling the result function. I know that the app is making the calls and 
> > getting the resulting XML (using Firebug). I can set a breakpoint anywhere 
> > else in the app and it will stop...just not on the result or fault HTTP 
> > service functions.
> > 
> > Also, I only have this problem on this one component. This doesn't happen 
> > anywhere else in the application. I would paste some code in here for you 
> > to evaluate - but I doubt it will be useful. If I change the name of the 
> > function in the result="" then Flex warns me that I'm referencing a 
> > function that doesn't exist. So when I retype it to match the function 
> > below...the warning disappears.
> > 
> > The only other thing I can mention is that I "accidentally" installed Flash 
> > 10 player, so I uninstalled and then installed Flash 9 Active-X Debugger. 
> > But again...I only have this issue on one component.
> > 
> > Any initial thoughts/ideas?
> > 
> > Thanks to all!
> >
>


Reply via email to