Yep, I guess it was getting cached... I added the timestamp stuff that was in both of the responses here, and that took care of it -- fresh data every time.
Thanks! L. --- In [email protected], dorkie dork from dorktown <dorkiedorkfromdorkt...@...> wrote: > > it's prob accessing it from the cache. > > instead of this, > url="reports/xml/{_reportInfo.fileName}.xml" > > use this: > url="reports/xml/{_reportInfo.fileName}.xml?time={getTimer()}" > > that snippet might not be bindable so add the time in code whenever you > access that file > > On Tue, Aug 17, 2010 at 6:17 PM, Laurence <lmacne...@...> wrote: > > > > > > > Ok. I have the following HTTP Service declared: > > <mx:HTTPService id="reportDataRPC" > > url="reports/xml/{_reportInfo.fileName}.xml" > > result="rdHandler(event);" > > fault="rpcFaultHandler(event);"/> > > > > In the init() function (which is called when the 'show' event happens, > > because the page it's on happens to be part of a ViewStack) I have the > > following line: > > reportDataRPC.send(); > > > > This loads the data from the .xml file and in the "rdHandler" function lets > > me put that data into my various ArrayCollections and whatnot... That's > > working fine... At least, the FIRST time... > > > > Every subsequent time, the result-set is exactly the same as the first time > > -- even if the .xml file it's reading has changed in the interim. > > > > If I completely shut-down the program and re-load it, then I finally get > > the new .xml file in there. > > > > So, how do I get it to give me a complete refresh of the data? I've tried > > calling 'reportDataRPC.clearResult()' and 'reportDataRPC.disconnect()' after > > storing the data in my ArrayCollections, but that didn't seem to do anything > > at all... > > > > I'm at a complete loss -- it's totally unacceptable to not be able to get > > the new data when the underlying .xml file changes. Can someone point me in > > the right direction? > > > > Thanks, > > Laurence MacNeill > > Mableton, Georgia, USA > > > > > > >
