Flex 2 Compatibility? Seeing StreamingAMFChannel compile error

Question

I have seen postings such as <br />http://tjordahl.blogspot.com/2008/03/blazeds-and-flex-2-compatibility.html<br />suggesting that BlazeDS is compatible with the latest versions of Flex 2 SDK.<br /><br />My experience shows that this may not be completely true.<br /><br />In Flex Builder 3, I have created a project using Flex 2.0.1 Hotfix 3 SDK.<br />This points to:<br />C:\Program Files\Adobe\Flex Builder 3\sdks\2.0.1<br />which is build 180927.<br /><br />I have code like this:<br /><br />public function sendRequest(): void {<br />        var ro:RemoteObject = new RemoteObject();<br />        ro.addEventListener(ResultEvent.RESULT, resultHandler);<br />        ro.addEventListener(FaultEvent.FAULT, faultHandler);                  <br />                  <br />             <br />     if (_channelId != null && _channelUrl != null)<br />        {<br />   var cs:ChannelSet = new ChannelSet();<br />                    <br />   var myChannel:AMFChannel = new AMFChannel(_channelId, _channelUrl);<br />   myChannel.pollingEnabled = true;<br />   myChannel.pollingInterval = 8000;<br />   cs.addChannel(myChannel);<br />   ro.channelSet = cs;<br />        }<br />               <br /><br />   ro.destination = "myService";<br />   ro.channelSet = cs;<br />                                   <br />   ro.myOperation();               <br />}<br /><br />When compiling this I get the following error message:<br /><br />Channel definition, mx.messaging.channels.StreamingAMFChannel, can not be found.<br /><br />Even when I comment out the above code referencing AMFChannel, the compile error still occurs (even when doing a "clean" build).<br /><br />Here are the relevant compiler settings:<br /><br /><?xml version="1.0" encoding="UTF-8"?><br /><actionScriptProperties mainApplicationPath="client.mxml" version="3"><br /><compiler additionalCompilerArguments="-services &quot;C:\tomcat_blazeDS\webapps\myservice\WEB-INF\flex\services-config.xml&quot;<br />  -locale en_US" copyDependentFiles="true" enableModuleDebug="true" flexSDK="Flex 2.0.1 Hotfix 3" generateAccessible="false"<br />   htmlExpressInstall="true" htmlGenerate="true" htmlHistoryManagement="true" htmlPlayerVersion="9.0.28" htmlPlayerVersionCheck="true" <br />   outputFolderLocation="C:/tomcat_blazeDS/webapps/myservice/swf" outputFolderPath="bin-debug" sourceFolderPath="src" <br />   strict="true" useApolloConfig="false" verifyDigests="true" warn="true"><br /><compilerSourcePath/><br /><libraryPath defaultLinkType="1"><br /><libraryPathEntry kind="4" path=""><br /><modifiedEntries><br /><libraryPathEntry kind="3" linkType="4" path="${PROJECT_FRAMEWORKS}/libs/framework.swc" useDefaultLinkType="true"><br /><crossDomainRsls><br /><crossDomainRslEntry autoExtract="true" policyFileUrl="" rslUrl="framework_3.0.0.477.swz"/><br /><crossDomainRslEntry autoExtract="true" policyFileUrl="" rslUrl="framework_3.0.0.477.swf"/><br /></crossDomainRsls><br /></libraryPathEntry><br /></modifiedEntries><br /></libraryPathEntry><br /><libraryPathEntry kind="1" linkType="1" path="libs"/><br /><libraryPathEntry kind="3" linkType="1" path="myCore.swc" useDefaultLinkType="false"/><br /></libraryPath><br /><sourceAttachmentPath/><br /></compiler><br /><applications><br /><application path="client.mxml"/><br /></applications><br /><modules/><br /><buildCSSFiles/><br /></actionScriptProperties><br /><br />Any comments on whether this should work, and is supported?  If this is expected to work, I would also appreciate some ideas on work-arounds.<br /><br />Thank you,<br />David

Answer 1

David,
Even when you comment out the channel (actually all channels) that has the
reference to mx.messaging.channels.StreamingAMFChannel this still doesn't
work?
Are you sure that FlexBuilder is pointing at the right services-config.xml
file when it compiles the MXML? It can't point at a BlazeDS 'default'
config.
It sounds like the problem is that the Flex2 libraries in the swf are trying
to load that channel class which is new for Flex3 and it isn't there.
Removing any and all references to this class in the config files used to
compile the swf should fix it.
Let us knwo if that isn't it.
Tom Jordahl