> Maybe I wasn't clear in my question. When you run the FalconJX compiler, > it generates both a bin/js-debug/index.html and a > bin/js-release/index.html. The one in js-release could have more issues > since it allows for property renaming. I'm trying to determine if you > have tried the version in bin/js-debug/index.html.
I always tests by bin/js-debug/index.html only, I have seen bin/js-release/index.html does almost nothing in browser - maybe the reasons you described is why the js-release version not working expectedly. > If you have, it is probably worth checking with a Network Monitor to see > if the HTML version is requesting the same URL as the SWF version and > whether the same data comes back. I am in downloading process of a http monitor software to my MacOS, until then I've tested through debugging in Firebug. I confirm the calling URL is as it supposed to be, HTTPService.complete handler shows no HTTPService.target.data/json property, contentData property showing null. > Can you put together a small test case? A JSONInputParser is handed the > HTTPService.data property so for it to work but your own access to > HTTPService.data does not work is rather strange. I'm sending you the demo project I'm working on so the test URL will be same as mine. Click on 'Reload Data' button upon application starts in browser. Things I want to note against this source: 1. HTTPService.lazyCollection do not uses any JSONItemConverter 2. HTTPService.lazyCollection uses an instance of JSONInputParser class without extending it 3. This worked in OSX Safari as HTML but Firefox 4. Previously when I added custom JSONItemConverter I found OSX Firefox working, but Chrome and IE in Windows failing. https://www.dropbox.com/s/fut9y55zih4qojc/TestFlexJSTableForAlex.zip?dl=0 -- View this message in context: http://apache-flex-users.2333346.n4.nabble.com/FlexJS-HTTPService-for-XML-parsing-tp12094p12146.html Sent from the Apache Flex Users mailing list archive at Nabble.com.
