This content has been marked as final. Show 6 replies
hmmmm, did you try catching an ErrorEvent? It is a different type than a FaultEvent. There's even an IOErrorEvent, but it is a subclass of error event, so if you catch the error event, you should be able to catch both.
This was a good suggestion. Thank you. Unfortunately the addition of ErrorEvent did not have any effect.
It is obivious I am not thinking today... bad cold.... yeah, that's it
How about a try-catch block. That should do the trick.
I'm not really sure why I didn't think of that first.
Since this is an asynchronous process a try/catch block will not work. The code is already out of the "send" when the error occurs. I would think that an error event of some kind will be necessary. It just doesn't seem to work.
Yep, you are right. I'm still not thinking correctly... anyway...
Are you working out of Flex Builder2? You might be able to get a stack trace to determine the class hierarchy that this error is coming from.
Of course, the thing to do is actually determine where this error is originating from and fix it, instead of the symptoms. But, being that this error is not really descriptive and everything seems to be working, this might be your only course of action.
You may also want to try using method="POST" on your HTTPService. That might clear it up.
Is this just a file on a Web Server that you are retrieving?
This is a static xml file. There is not get/post. No parms of any kind. This does not occur during use of Flex Builder 2. It only happens when the swf is being retrieved via server.
Since this is the only stream I think it is safe to say that this is the stream throwing the error.