Yay! Declarative mxml is handy, but you will find *many* advantages to doing that kind of stuff in AS code.
Tracy ________________________________ From: flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] On Behalf Of weezee49 Sent: Wednesday, January 07, 2009 6:47 PM To: flexcoders@yahoogroups.com Subject: [flexcoders] Re: error in HTTPService Thanks, everyone. It appears that the <mx:request> object isn't refreshed the 2nd time around. A network utility wasn't needed because the message wasn't getting out of the client - the server log didn't register any requests. Stepping through the code showed that it was dying in the HTTPService, never reaching the handleSimUpdateResult() function. I solved the problem by doing what Tracy suggested - building the XML in a function each time I need to send an update or a create request. LG Rains --- In flexcoders@yahoogroups.com <mailto:flexcoders%40yahoogroups.com> , "Tracy Spratt" <tspr...@...> wrote: > > Also, a declaratively created request object is very difficult to debug. > I suggest you build that XML in an as function, then trace it out and > verify it is valid as a whole. I suspect that you have invalid xml the > second time. > > > > Using a utility will also let you do this, but simply tracing the XML > might be simpler. > > > > Tracy >
