Deployment problem mx:HTTPService

[Chip Thomas]

We developed a Flex application in a local RAD/Websphere development
environment where it works fine. However after we loaded to the QA
environment the data referenced by the application appears to fail to be
delivered to the swf program.

The Flex application uses mx:HTTPService to identify the source of the data
thusly....

<mx:HTTPService
id="esData"

url="/ShareholderInformationPortal/ExecutiveSummary.do?requestFor=ResponseData&
amp;xml=true"
useProxy="false"/>

This url will cause the application server to obtain data from a database, and
send back an XML formatted page. It also happens to display the data in the
log (for testing purposes). In both the local and QA environment we see the
data in the log, so we know that it is being obtained from the database.
However the data is only populated in the flex application that runs locally.

There are a number of differences between the local and QA server. Most of
these can be controlled and eliminated. Specifically, QA goes through a Apache
server, but the Apache server can and has been bypassed by adjusting the URL.
QA also tends to use a proxy, but this can and has been be turned off.

The only real differences we can clearly establish is that QA runs on
Websphere 6.1.0.13 and the local server runs 6.1.0.2. Another difference is
that local testing has all been on a local LAN and the QA server is relatively
"far away" on the corporate network.

Does anyone have any ideas?

Thanks.
Chip

[ab1301]

Sounds like you do not have a crossdomain policy installed on the server. Look it up. It's an easy fix if this is the problem.

[Chip Thomas]

My understanding was that you only needed a cross-domain policy if the resource
you were accessing was different from that which the swf file was loaded. In
this case they are the same domain. In fact they would have to be since the
URL specified in the mx:HTTPService is not absolute, but relative.

Is there something I have wrong?