This content has been marked as final. Show 8 replies
C'mon folks, anyone got any ideas here? I'm freakin desperate. This is such a simple and basic issue that if I can't resolve it, I can't use Flex. I'm at a dead standstill here.
It means your output was not formed correctly and could not be parsed. set up a server side script or something to check that the output is indeed what you think it should be, 99% of the time i get thie error its due to malformed output from my webservice or db. Also try making an xml model of your target data to test the application internaly, look up model in the docs, it easy to use and if the model works then you know the data is faulty and you need to check your output and queries.
I don't think that's happening, because Flex isn't even hitting the web server to get the data.
It hits the web server to get the WSDL, then it hits it again for the one web service that works, but the web server sees NO traffic when I try to run the queryDB() method.
The web service, btw, is a coldfusion component.
like i said, build a model and test it, then you will KNOW if its the data or not
It's not the data. The flex app isn't even *GETTING* the data. It's not even CALLING the CFC. Thus it cannot be the data.
You can view the data returned by the CFC using the tinyurl above, however, none of that data is getting to Flex because the queryDB method is *NOT* being called. The request isn't getting through to the web service.
You should turn on logging and take a look at the request and response that get logged to flashlog. To do so add this:
<mx:TraceTarget level="0" />
This should hopefully shed some light.
Unfortunately, I don't know exactly *HOW* I solved it. I ended up making an alternative web service that used fewer arguments and was simpler.. and worked backwards to add the necessary stuff back in. I just don't know why it works now because it's essentially the same everything.
Thanks for the flashlog tip - I will definately keep that in mind for the future!