I'm trying to save myself a few minutes and my brain... may be a waste of
effort but I'm
hoping someone can help.
My local test environment is not SSL - our dev and production environments are.
We have
the services-config and remote configs set up properly no problem... everything
works.
Except, when testing locally, we put
<mx:RemoteObject id="RemoteUserService" destination="ColdFusion"
showBusyCursor="true" source="mbfnetperf.remote.RemoteUserService">
and when pushing out to dev/production, we have to change to:
<mx:RemoteObject id="RemoteUserService" destination="SecureColdFusion"
showBusyCursor="true" source="mbfnetperf.remote.RemoteUserService">
so i thought i could simply do:
destination="{servicesDestination}"
debug shows a valid value of "ColdFusion" in the variable "servicesDestination"
but the call
fails
[MessagingError message=''null' is not a valid destination.']
I don't want to recode all of the MXML calls to AS (it probably wouldn't take
forever) but i
was just wondering if there's a simple answer instead of rewriting
Thanks for any ideas - haven't found a solution in the archives
