I am using remote objects to collect data from my db
and pass it to my
flex front end. I built a test app to make sure that I am getting
connectivity from flex to my cf server. I have also added the the
destination RETS to the services-config.xml file.
I have had this problem previously, and restarting fb would clear it
up because the services-config.xml file was cached. Now not even this
will do it. I know my destination is correct because I have
included/output it in my flex app.
This is the error that I get.
faultCode:Server.Processing faultString:'No destination 'RETS' exists
in service flex.messaging.services.RemotingService' faultDetail:'null'
but in my output from my Services.xml file, I have this. I can clearly
see that I have the destination RETS set in my services-config.xml file.
<services>
<coldfusion-flashremoting-service
messageTypes="flex.messaging.messages.RemotingMessage">
<destination id="RETS">
<channels>
<channel ref="my-cfamf"/>
</channels>
</destination>
<destination id="ColdFusion">
<channels>
<channel ref="my-cfamf"/>
</channels>
</destination>
</coldfusion-flashremoting-service>
<channels>
<channel id="my-cfamf" type="mx.messaging.channels.AMFChannel">
<endpoint uri="http://beta.homesmartagent.com/flex2gateway/"/>
<properties>
<polling-enabled>false</polling-enabled>
</properties>
</channel>
</channels>
</services>
Here is the full desination from my services-config.xml file.
<destination id="RETS">
<channels>
<channel ref="my-cfamf"/>
</channels>
<properties>
<source>com.RetsSearch</source>
<!-- define the resolution rules and access level
of the cfc being invoked -->
<access>
<!-- Use the ColdFusion mappings to find CFCs,
by default only CFC files under your webroot can be found. -->
<use-mappings>false</use-mappings>
<!-- allow "public and remote" or just
"remote" methods to be invoked -->
<method-access-level>remote</method-access-level>
</access>
<property-case>
<!-- cfc property names -->
<force-cfc-lowercase>false</force-cfc-lowercase>
<!-- Query column names -->
<force-query-lowercase>false</force-query-lowercase>
<!-- struct keys -->
<force-struct-lowercase>false</force-struct-lowercase>
</property-case>
</properties>
</destination>
