Based on restful annotations (spring4.0.2 integration Flex+blazeds+spring-mvc) __blazeds

This article turns from: http://www.blogjava.net/liuguly/archive/2014/03/10/410824.html

Reference website: 1.http://livedocs.adobe.com/blazeds/1/blazeds_devguide/
2.http://docs.spring.io/spring-flex/docs/1.5.2.release/reference/html/

1) Download blazeds (turnkey4.0.x version) URL: http://sourceforge.net/adobe/blazeds/wiki/Home/
2 Create MAVEN Project first, then enter BlazeDS directory/tomcat/webapps/blazeds/web-inf/flex even the Flex directory copy to Src/main/resource directory (also can directly copy files)
As shown in figure:

3 Core flex-related JAR pack
Download Spring-flex-core-1.5.2.release.jar
Blazeds-core-4.0.0.14931.jar
Blazeds-common-4.0.0.14931.jar
Blazeds-proxy-4.0.0.14931.jar
Blazeds-remoting-4.0.0.14931.jar
Where Spring-flex-core-1.5.2.release.jar can be downloaded from the Remote MAVEN Center repository, while the BlazeDS jar is in the Center warehouse version incorrectly, as shown in the figure:

When the spring container starts, spring-flex-core-1.5.2 relies on the
The 4.0.0.14931 version of BlazeDS, and the MAVEN center repository does not have this jar package, so the above four packages need to be manually entered into the local MAVEN warehouse to enter the command
Enter the BlazeDS directory/resources/lib execute the following MAVEN command
MVN install:install-file-dpackaging = Jar-dgroupid = Com.adobe.blazeds-dversion = 4.0. 0.14931-dartifactid = Blazeds-common-dfile = Flex-messaging-common.jar

MVN install:install-file-dpackaging = Jar-dgroupid = Com.adobe.blazeds-dversion = 4.0. 0.14931-dartifactid = Blazeds-core-dfile = Flex-messaging-core.jar

MVN install:install-file-dpackaging = Jar-dgroupid = Com.adobe.blazeds-dversion = 4.0. 0.14931-dartifactid = Blazeds-opt-dfile = Flex-messaging-opt.jar

MVN install:install-file-dpackaging = Jar-dgroupid = Com.adobe.blazeds-dversion = 4.0. 0.14931-dartifactid = Blazeds-proxy-dfile = Flex-messaging-proxy.jar

MVN install:install-file-dpackaging = Jar-dgroupid = Com.adobe.blazeds-dversion = 4.0. 0.14931-dartifactid = Blazeds-remoting-dfile = Flex-messaging-remoting.jar to this point, the associated jar package can be introduced into the project.
4) Configure Flex/services-config.xml file red for modified content
Channel for Flex, the equivalent of a communication pipeline, on the flex client side performance is endpoint= "The following red font Endpoint.url properties"
1.? XML version = "1.0" encoding = "UTF-8"?>
2 < Services-config >
3
4 < Services >
5 < Service-include File-path = "Remoting-config.xml"/>
6 < Service-include File-path = "Proxy-config.xml"/>
7 < Service-include File-path = "Messaging-config.xml"/>
8 </Services >
9
< security >
One < Login-command class = "Flex.messaging.security.TomcatLoginCommand" server = "Tomcat"/>
<!--uncomment the correct app server
< Login-command class = "Flex.messaging.security.TomcatLoginCommand" server = "JBoss" >
< Login-command class = "Flex.messaging.security.JRunLoginCommand" server = "JRun"/>
< Login-command class = "Flex.messaging.security.WeblogicLoginCommand" server = "Weblogic"/>
< Login-command class = "Flex.messaging.security.WebSphereLoginCommand" server = "WebSphere"/>
-->
18
<!--
< Security-constraint ID = "Basic-read-access" >
< Auth-method > Basic </auth-method >
< roles >
< role > Guests </role >
< role > Accountants </role >
< role > Employees </role >
< role > Managers </role >
</Roles >
</security-constraint >
-->
</Security >
31
< channels >
33
< channel-definition ID = "MY-AMF" class = "<