Very nice, Ken. Glad to see it was finally sorted out. You have unlocked the door that I was alluding to in my comment in Ben's entry:

"I wonder if all this issue simply boils down to (all of) us needing help better understanding what parts of the Flex Builder Wizard setup steps regard the config of the local machine on which development is taking place versus what parts relate to the actual server on which deployment will take place.

Looking at it another way, many have used RDS features in connection with a localhost to do page creation, and then later deployed that code on a remote server. What we have here is an obvious need to get more info on what parts of the setup of the wizard need to reflect the server WHERE THE CODE WILL BE DEPLOYED."

That Flex Server Tab entry for the Flex server URL seems to be the key, right?.

Kenny Silanskas:

I'm sorry - I haven't successfully run it with the old flash remoting Endpoint, but have been told it should work.

Perhaps Jeff or Charlie has successfully done this and can chime in?

<?xml version="1.0" encoding="UTF-8"?>
<services-config>

<services>
<service id="coldfusion-flashremoting-service"
class="flex.messaging.services.RemotingService"
messageTypes="flex.messaging.messages.RemotingMessage">

<adapters>
<adapter-definition id="cf-object" class="coldfusion.flash.messaging.ColdFusionAdapter" default="true"/>
</adapters>

<destination id="ColdFusion">
<channels>
<channel ref="my-cfamf"/>
</channels>
<properties>
<source>*</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>

</service>
</services>

<channels>
<channel-definition id="my-cfamf" class="mx.messaging.channels.AMFChannel">
<endpoint uri="http://{server.name}:{server.port}{context.root}/flex2gateway/" class="flex.messaging.endpoints.AMFEndpoint"/>
<properties>
<polling-enabled>false</polling-enabled>
<serialization>
<instantiate-types>false</instantiate-types>
</serialization>
</properties>
</channel-definition>
</channels>

<logging>
<target class="flex.messaging.log.ConsoleTarget" level="Error">
<properties>
<prefix>[Flex] </prefix>
<includeDate>false</includeDate>
<includeTime>false</includeTime>
<includeLevel>false</includeLevel>
<includeCategory>false</includeCategory>
</properties>
<filters>
<pattern>Endpoint.*</pattern>
<pattern>Service.*</pattern>
<pattern>Configuration</pattern>
<pattern>Message.*</pattern>
</filters>
</target>
</logging>

<system>
</system>

</services-config>

Ken,

I am having trouble getting this to work. I am developing everything locally (using IIS w/ CF Developer Edition) and I cannot get rid of this error. Any ideas would help greatly. Is their something I missed during the install?

Thanks for the illumination!

What I'd like to know is how to get the wizard to generate the code so that it points the remote object to the correct source without having to do a search and replace each time I need to regenerate the code:

Example:
my APP ROOT:
http://localhost/sites/flex/db1
the file location:
is c:\sites\flex\db1

App Wizard Assumes it's being deployed off the webroot.

Realistically, most of us don't expect to deploy their crud apps off the webroot. More likely scenerio we'd deploy webroot /admin or /webapps or /flex etc.

So is this a limitation of the app wizard? Or can one "configure" the wizard to use a more accessable webroot and site folder?



Examples:

One needs to change this:
<mx:RemoteObject
      id="dataManager"
      showBusyCursor="true"
      destination="ColdFusion" source="db1.components.cfgenerated.companies">
      <mx:method name="getMasterQuery" result="getMasterQuery_result(event)" fault="server_fault(event)" />
      <mx:method name="deleteItem" result="deleteItem_result(event)" fault="server_fault(event)" />
   </mx:RemoteObject>

to to this:

<mx:RemoteObject
      id="dataManager"
      showBusyCursor="true"
      destination="ColdFusion" source="sites.flex.db1.components.cfgenerated.companies">
      <mx:method name="getMasterQuery" result="getMasterQuery_result(event)" fault="server_fault(event)" />
      <mx:method name="deleteItem" result="deleteItem_result(event)" fault="server_fault(event)" />
   </mx:RemoteObject>

Hi Ken,

I'm hosting with crystaltech.com and struggling to get the Phones app working.

You said:

"4. In your flex app, reference your RemoteObject's source as folderofyourapp.cfcname (without the .cfc at the end)"

Where exactly in the Server Properties do I enter this? I have three text entry boxes named:

Root Folder
Root URL
Context Root

Also, do I need to know where my CFIDE is located. One of the errors that was thrown up says it can't find the CFIDE path. Surely I would need to make changes to services-config.xml depending on where CFIDE is located.

Cheers,
Paul

I am having trouble getting this to work. I am developing everything locally (using IIS w/ CF Developer Edition) and I cannot get rid of this error. Any ideas would help greatly. Is their something I missed during the install?
http://www.dir-9.com

Thanks for help, Keep up the good work.