That’s really weird. I would suggest
to strip down the code to minimum. Drop out the showBusyCursor (set it to
false), try to call service several times with different params and see what
happens. On faulthandler I believe you should have mx.core.Application.alert(event.fault)
instead of event.result. If that does not help anything, then I
would change the data returned by the server to minimum (ie to just a String)
to see if it’s a data convert error (from Java to flex) and try to work
from there up to the problem. I have worked with remote objects for over
a year now and only problems that I’ve encountered have been some conversion
errors (that sometimes fail silently!) and some problems with responder objects
that were actually a bug in my code. And we do run long methods too, some may
take as much as 5 minutes and they do return results and come back alive. -Mika From: Hi, -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com
SPONSORED LINKS
YAHOO! GROUPS LINKS
__,_._,___ |
- [flexcoders] Flex Timeout issue digital_eyezed
- RE: [flexcoders] Flex Timeout issue Mika Kiljunen
- [flexcoders] Re: Flex Timeout issue digital_eyezed
- RE: [flexcoders] Re: Flex Timeout issue Mika Kiljunen
- [flexcoders] Re: Flex Timeout issue digital_eyezed