When you use the Flex Builder Project Setup Wizard and select ColdFusion as the server type, the wizard configures Flex Builder to use the services-config.xml file for you. Use the following steps to configure your project:

1. Select File> New> Flex Project to open the New Flex Project Wizard. and enter the appropriate information in the first sections of the Create a Flex project page.

2. Select one of the radio buttons, as follows:

   • Select ColdFusion Flash Remoting to compile in Flex Builder.

   • If you installed LiveCycle Data Services with ColdFusion and want to use messaging or data management, select Flex Data Services.

3. If you select Flex Data services, select whether to compile the application locally in Flex Builder or on the application server where the page is viewed. Do not select to compile code that you deploy on the server; this option is for development purposes only.

4. Click Next and complete creating the project, then click Finish.

If you select Basic on the first Create a Flex Project page, and decide later to compile the application for use with ColdFusion, configure Flex Builder manually, as follows:

1. Select Project > Properties.

2. Select Flex Complier in the right pane of the Properties dialog.

3. In the Additional Compiler arguments add -services= followed by the absolute path to the services-config.xml file in the local ColdFusion installation. For example, on a Windows system with a default ColdFusion stand-alone installation, specify the following argument string.

   -services=C:/ColdFusion9/wwwroot/WEB-INF/flex/services-config.xml

When you use the Flex Builder Project Setup Wizard and select ColdFusion as the server type, the wizard configures Flex Builder to use the services-config.xml file for you. Use the following steps to configure your project:

1. Select File> New> Flex Project to open the New Flex Project Wizard. and enter the appropriate information in the first sections of the Create a Flex project page.

2. In the Server technology section of the Create a Flex project page, select ColdFusion as the Application server type, and select Use remote object access service.

3. Select one of the radio buttons, as follows:

   • Select ColdFusion Flash Remoting to compile in Flex Builder.

   • If you installed LiveCycle Data Services and want to compile the application on the server, select LiveCycle Data services in Flex Builder 3.

4. Click Next to open the Configure ColdFusion page, and enter the required information. If you selected LiveCycle Data services in step 3, you can select to compile the application locally or on the server. Select to compile on the server only when you are developing your application, for convenience. Do not select to compile on the server code that you deploy, because the MXML page is not compiled to a SWF file until the user requests it, and the compiler does not create an HTML wrapper page.

5. Click Finish to complete the configuration.

If you do not specify ColdFusion in the Server technology section of the Create a Flex project page, and decide later to compile the application for use with ColdFusion, configure Flex Builder manually, as follows:

1. Select Project > Properties.

2. Select Flex Complier in the right pane of the Properties dialog.

3. In the Additional Compiler arguments add -services= followed by the absolute path to the services-config.xml file in the local ColdFusion installation. For example, on a Windows system with a default ColdFusion stand-alone installation, specify the following argument string.

   -services=C:/ColdFusion8/wwwroot/WEB-INF/flex/services-config.xml

To specify the CFC in your MXML, use code such as the following:

<mx:RemotObject 
    id="myCfc" 
    destination="ColdFusion" 
    source="myApplication.components.User"/>

ColdFusion 9 supports BlazeDS that allows messaging support for ColdFusion. When you install ColdFusion, the following files are added to the /WEB-INF/flex directory:

• remoting-config.xml

• messaging-config.xml

• services-config.xml

• proxy-config.xml

The destination ColdFusion is preconfigured in remoting-config.xml. The default source value for this destination is the wildcard, *. For more information about the changes in Flash Remoting for ColdFusion 9, see Changes in the XML configuration files for Flash Remoting in ColdFusion 9.

You do not have to use the ColdFusion destination if you have configured other valid destinations in the configuration file. In this case, the destination definition must specify * as the value of its source element. If you specify a source other than * in remoting-config.xml, then that source definition overrides the source specified in the MXML.

For details of defining a destination, see Create a named resource for a CFC.

1. Edit the WEB-INF/flex/remoting-config.xml file by adding a destination entry for the CFC, for example:

   <service id="remoting-service" class="flex.messaging.services.RemotingService" messageTypes="flex.messaging.messages.RemotingMessage"> 
       <adapters> 
       <adapter-definition id="cf-object"      
       class="coldfusion.flash.messaging.ColdFusionAdapter" default="true" /> 
       <adapter-definition id="java-object" 
       class="flex.messaging.services.remoting.adapters.JavaAdapter" /> 
       </adapters> 
    
           <default-channels> 
           <channel ref="my-cfamf" /> 
           </default-channels> 
               <destination id="ColdFusion"> 
           <channels> 
    
           <channel ref="my-cfamf" /> 
           </channels> 
           <properties> 
           <source>*</source> 
           </properties> 
       </destination> 
   </service> 

   The source attribute specifies the dot notation to the CFC from the web root (the classpath to the CFC).

   The channel-ref tag refers to the channel-definition in the services-config.xml file. In the preceding sample, the my-cfamf channel-definition has been referenced, which looks similar to the following:

   <channel-definition id="my-cfamf" class="mx.messaging.channels.AMFChannel"> <endpoint uri="http://{server.name}:{server.port}{context.root}/flex2gateway/" class="coldfusion.flash.messaging.CFAMFEndPoint" /> 
       <properties> 
           <polling-enabled>false</polling-enabled> 
           <serialization> 
               <enable-small-messages>false</enable-small-messages> 
           </serialization> 
           <coldfusion> 
               <access> 
                   <use-mappings>true</use-mappings> 
                   <method-access-level>remote</method-access-level> 
               </access> 
               <use-accessors>true</use-accessors> 
               <use-implicit-accessors>false</use-implicit-accessors> 
               <use-structs>false</use-structs> 
               <property-case> 
                   <force-cfc-lowercase>false</force-cfc-lowercase> 
                   <force-query-lowercase>false</force-query-lowercase> 
                   <force-struct-lowercase>false</force-struct-lowercase> 
               </property-case> 
           </coldfusion> 
       </properties> 
   </channel-definition>

2. Restart the ColdFusion server.

The following table describes the XML attributes for remoting-config.xml:

The following table lists the XML attributes for services-config.xml:

force-cfc-lowercase
force-query-lowercase
force-struct-lowercase 

1. In the MXML file, you use the <mx:RemoteObject> tag to connect to your CFC named resource. With this connection, you can call any remote method on the CFC.

2. If you created a destination for the CFC in the remoting-config.xml file, specify the destination name in the mx:RemoteObject tag; for example:

   <mx:RemoteObject  
       id="a_named_reference_to_use_in_mxml"  
       destination="CustomID"  
       result="my_CFC_handler(event)"/> 

   If you did not create a destination for the CFC, specify the ColdFusion destination and the CFC path in the mx:RemoteObbject tag; for example:

   <mx:RemotObject 
       id="myCfc" 
       destination="ColdFusion" 
       source="myApplication.components.User"/>

3. Call a CFC method, for example, as the following example shows:

   <mx:Button label="reload" click="my_CFC.getUsers()"/> 

   In this example, when a user presses a button, the Click event calls the CFC method getUsers.

4. Specify a handler for the returned result of the CFC method call for the <mx:RemoteObject> tag, as the following example shows.

   private function my_CFC_handler( event:ResultEvent ) 
   { 
   // Show alert with the value that is returned from the CFC. 
   mx.controls.Alert.show(ObjectUtil.toString(event.result)); 
   }

To compile and run an application using Flash Builder, make sure that Flash Builder is configured as described in Configure Flex Compilation. Compile your application normally to create a SWF file. When you configure your Flash Builder project you can specify the location in which to place it. By default, Flash Builder attempts to place the SWF file and an HTML wrapper page under the web root. You can then run the application as appropriate, for example, by requesting the HTML wrapper for the SWF file in a browser.

To compile the application directly using the SDK, set the Flex compiler to use the ColdFusion services-config.xml file. Set the Flex compiler by adding to the mxml command line “ -services=” followed by the absolute path to the services-config.xml file in the local ColdFusion installation. For example, on a Windows system with a default ColdFusion standalone installation, specify the following argument string.

-services=C:/ColdFusionCentuar/wwwroot/WEB-INF/flex/services-config.xml