- deployed BlazeDS jars to one single Group ID – com.adobe.blazeds
- flex-messaging-common 4.0.0.14931
- flex-messaging-core 4.0.0.14931
- flex-messaging-opt 4.0.0.14931
- flex-messaging-proxy – 4.0.0.14931
- flex-messaging-remoting – 4.0.0.14931
- cfgatewayadapter – 4.0.0.14931
- xalan – 2.6.0
- flex-rds-server 1.5.0
- commons-codec – 1.3
- commons-httpclient – 3.0.1
- commons-logging – 1.0.4
- finally got BlazeDS up and running from Maven
- flexmojos:flexbuilder doesn’t create project files properly for Flex SDK 4.0, manually add name spaces
- change <mx:Application> tag to <s:Application>
- xmlns:fx=”http://ns.adobe.com/mxml/2009″ xmlns:s=”library://ns.adobe.com/flex/spark” xmlns:mx=”library://ns.adobe.com/flex/mx”
- Flex 4 webapps needs some dependencies? These are added to the output directory from Flash Builder, but not included from pom.xml…. causing Remote Methods to fails and other problems….. updated pom to use these, but fails!!!!
- framework_4.5.0.17689.swc
- mx_4.5.0.17689.swc
- osmf_1.0.0.16316.swc
- rpc_4.5.0.17689.swc
- spark_4.5.0.17689.swc
- sparkskins_4.5.0.17689.swc
- textLayout_2.0.0.139.swc
- using Flex 4.0 SDK results in different swc’s
- framework_4.0.0.14159.swf
- osmf_flex.4.0.0.13495.swf
- rpc_4.0.0.14159.swf
- spark_4.0.0.14159.swf
- sparkskins_4.0.0.14159.swf
- textLayout_1.0.0.595 ????? 4.0.0.14159?
- turned out Maven builds swc included
- services configuration needed in Flex Project in order to work with BlazeDS – source/main/resources directory
