Adobe 38043740 - ColdFusion Standard - Mac Development Manual page 679

DEVELOPING COLDFUSION 9 APPLICATIONS
Flex and AIR Integration in ColdFusion
ColdFusion 9 supports Old XML configurations files as well, but with these files it will not be using Enhanced Flash
Remoting. To take advantage of Enhanced Flash Remoting, while migrating your old XML files to ColdFusion9, you
should make sure that they comply with new XML structural changes.
If you are using LCDS with ColdFusion 9, then Flash Remoting works on LCDS 2.6.1. Ensure that you are on LCDS
2.6.1 to make use of the enhanced Flash Remoting.
ColdFusion 9 is backward compatible with old Flash Remoting as well, to support LCDS2.5 and prior releases.
Now in a case, where you require to continue with LCDS 2.5 or prior versions, it will not be possible for you to use
enhanced Flash Remoting offered by ColdFusion 9. In this scenario, you can continue working with LCDS2.5 and
prior versions with old style XML configuration files.
To use the old style flash remoting with LCDS 2.5, first remove the existing ColdFusion 9 flex-*.jar files from
by taking a backup of the files and placing the
cfusion/lib
After this, you can continue to use the old style (ColdFusion 8) XML configuration files by placing them under
directory. Also make sure that
INF\Flex\
For detailed steps on integrating LCDS2.5 with ColdFusion, see the technote on www.adobe.com.
Another case here could be that you have integrated LCDS 2.6.1 with ColdFusion 9 and still you want to use old Flash
Remoting. You can implement this scenario, but in this case you cannot take advantages offered by enhanced Flash
Remoting.
Changes in the XML configuration files for Flash Remoting in ColdFusion 9 and ColdFusion
9.0.1
For ColdFusion 9, the structure of the services-config.xml file has changed. These structural changes are:
• A new
tag has been added under the <properties> in
<coldfusion>
,
<access> <use-accessor>
In old ColdFusion 8 style remoting, these tags used to be present in the destination, defined in data-management-
config.xml file.
• Previously, the
<serialization>
<serialization>
<instantiate-types>false</instantiate-types>
</serialization>
However, now you need to either set the
file.
• The
<enable-small-messages>
Note: In case you create custom channel definition on your client side by overriding the XML-based channel
configurations, you still need to set "enableSmallMessages" flag to false. This is shown in the following code example:
<mx:ChannelSet id="myChannelSet">
<mx:channels>
<mx:AMFChannel enableSmallMessages="false"
url="http://localhost:8500/flex2gateway/cfamfpolling" id="cfAMFPolling"
pollingEnabled="true" pollingInterval="8"/>
</mx:channels>
</mx:ChannelSet>
• In ColdFusion 9, the endpoint class names have been changed from the endpoint classes in ColdFusion 8. The
following table provides a list of channel-definitions and their corresponding endpoint classes:
LCDS2.5 flex-*.jar
WEB-INF\ flex\jar\cfdataserviceadapter.jar
, , and
<use-structs> <property-case>
tag included:
<instantiate-types>
flag must be set to
false
Last updated 1/20/2012
files in the
<channel-definition>
tags are defined.
to or remove it from the services-config.xml
true
under the serialization property.
674
directory.
cfusion\lib
WEB-
is also present.
, where the