When tracking down connection errors, consider:
1. If it's HTTP, then think about crossdomain.xml
requirements. Are you hosting
your SWF on the same server that your connecting to? If not,
you may need
a crossdomain.xml policy file on the remote server.
2. Did you compile against the correct
/WEB-INF/flex/services-config.xml
by specifying its location through the -services command line
argument?
3. Do your endpoint urls make use of the {context.root}
token? If so, did
you provde the --context-root command line argument?
4. Are you trying to contact a secure endpoint url but did
not load the SWF
via HTTPS?
5. Have you considered adding <mx:TraceTarget level="0"
/> in your MXML and
using the debugger version of the Flash Player to watch the
subsequent trace
output in the flashlog.txt file?
6. If you think the problem is on the server, have you tried
changing the
logging level to "Debug" in /WEB-INF/flex/services-config.xml
and ensuring
that the Endpoint.* filter pattern is active for the current
logging target?
7. Did you remember to restart your web application if you
have made a change
to the services-config.xml file or any of its includes (such
as editing a
destination in a service include file?)
8. Are you sure that the destination you're contacting has
channels defined
(or is relying on a set of default channels for the service)
- or did you
programmatically create your own ChannelSet on the client in
ActionScript?
