Spring Flex 1.5配置指南：整合BlazeDS与Spring的详细教程

Spring

Flex

需积分: 10 49 浏览量更新于2024-07-31 收藏 144KB PDF 举报

身份认证购VIP最低享 7 折!

领优惠券(最高得80元）

本文档是Spring Flex配置指南，版本1.5.0.RELEASE，发布于2011年6月，由Jeremy Grelle（SpringSource）撰写。这份指南详细介绍了如何在Spring框架中集成BlazeDS，一种用于实现Java应用程序与Adobe ActionScript（Flex）之间的高效双向数据通信技术。 1. **Spring BlazeDS集成概述**： - **背景**：随着企业级应用的需求增加，Spring和Flex的结合能够提供强大的客户端-服务器交互能力。Spring BlazeDS Integration允许开发者在Spring MVC架构中无缝整合BlazeDS，简化了数据传输和处理。 - **依赖版本**：为了运行Spring BlazeDS 1.5，必须确保至少使用了相应的Spring和BlazeDS主要版本。具体版本要求在文中未列出，但读者需要查阅最新的官方文档或项目页面。 - **支持渠道**：指南提供了一个指向获取支持和进一步学习的路径，包括官方社区、论坛和开发者文档。 2. **配置和使用BlazeDS消息代理**： - **介绍**：这部分详细讲解了如何设置Spring的消息代理（Message Broker），它是BlazeDS的核心组件，负责处理Flex客户端和服务器端的通信请求。 - **配置Spring DispatcherServlet**：首先，需要在Spring Web.xml中配置DispatcherServlet，以便处理Flex应用程序的HTTP请求。 - **配置Message Broker**：在Spring配置文件中，配置消息代理的bean，包括连接工厂、适配器和其他必要的配置选项。 - **映射请求到Message Broker**：定义路由规则，使得客户端请求能够正确地到达对应的处理程序。 - **Flex客户端与Spring MVC控制器协作**：指南还展示了如何在使用Spring MVC控制器的同时，让Flex客户端能访问这些服务。 - **Spring管理的Destination使用**：阐述如何在Flex客户端中访问Spring管理的Destination，实现数据的发送和接收。 - **高级定制**：提供了一些高级配置选项，如自定义异常处理和消息拦截器，以适应特定的应用场景和需求。 - **自定义扩展**：指南还介绍了如何创建和使用自定义的异常翻译器和消息拦截器，以增强系统的灵活性和可扩展性。这篇文档是开发人员不可或缺的参考资料，涵盖了从基础配置到高级定制的Spring BlazeDS集成实践，帮助开发者充分利用Spring的轻量级特性与BlazeDS的实时通信能力，构建高效、可维护的富客户端应用。

资源详情

资源推荐

<servlet-name>Spring MVC Dispatcher Servlet</servlet-name>

<url-pattern>/messagebroker/*</url-pattern>

</servlet-mapping>

When using the message-broker config tag, a SimpleUrlHandlerMapping is installed that by default maps all

incoming DispatcherServlet requests to the Spring-managed MessageBroker using a /*path pattern. The

default mapping can be overridden by providing one or more mapping child elements. If you want to provide

your own HandlerMapping bean configuration, you can disable the default using the

disable-default-mapping attribute of the message-broker tag. The order of the installed

SimpleUrlHandlerMapping can be set (for complex scenarios where multiple handler mapping types are

installed in the same context) using the mapping-order attribute.

The SimpleUrlHandlerMapping in the Spring WebApplicationContext maps all requests to the Spring-managed

MessageBroker via the MessageBrokerHandlerAdapter. The default setup installed by the message-broker

config tag is equivalent to the following bean definitions:

<value>

/*=_messageBroker

</value>

</property>

</bean>

Channel definitions in the BlazeDS services-config.xml must correspond to the chosen mapping. For example,

to set up a typical AMF channel in BlazeDS that matches the above mapping strategy:

<channel-definition id="my-amf" class="mx.messaging.channels.AMFChannel">

<endpoint url="http://{server.name}:{server.port}/{context.root}/messagebroker/amf"

class="flex.messaging.endpoints.AMFEndpoint"/>

<polling-enabled>false</polling-enabled>

</properties>

</channel-definition>

See the BlazeDS documentation for more information on configuring communication channels in

services-config.xml.

2.5. Using Flex clients alongside Spring MVC Controllers

It could often be the case that your application needs to serve more than just Flex-based clients. For example,

you may be constructing a RESTful architecture that is meant to serve multiple client-types. You could

potentially even be consuming RESTful endpoints using the Flex HTTPService component. Spring MVC's

controller model provides a simple, flexible means to create such RESTful endpoints. In these sorts of hybrid

web application secenarios, you will need to consider an alternate mapping strategy.

The simplest approach is to use a hierarchical application context with multiple DispatcherServlets. In this

approach, you configure your main application layer (services, security, supporting infrastructure, etc) in a

parent context loaded via the ContextLoaderListener, and then configure all aspects of your Spring MVC

controllers in one child DispatcherServlet context, and all aspects specific to your Flex client in a separate

Spring

Version 1.5.0.RELEASE 4

child DispatcherServlet context. This approach could look as follows in web.xml:

<context-param>

<param-name>contextConfigLocation</param-name>

<param-value>

/WEB-INF/spring/*-context.xml

</param-value>

</context-param>

<listener-class>org.springframework.web.context.ContextLoaderListener</listener-class>

</listener>

<servlet-name>flex</servlet-name>

<servlet-class>org.springframework.web.servlet.DispatcherServlet</servlet-class>

<load-on-startup>1</load-on-startup>

</servlet>

<servlet-mapping>

<servlet-name>flex</servlet-name>

<url-pattern>/messagebroker/*</url-pattern>

</servlet-mapping>

<servlet-name>spring-mvc</servlet-name>

<servlet-class>org.springframework.web.servlet.DispatcherServlet</servlet-class>

<load-on-startup>1</load-on-startup>

</servlet>

<servlet-mapping>

<servlet-name>spring-mvc</servlet-name>

<url-pattern>/spring/*</url-pattern>

</servlet-mapping>

Here the parent application context is being assembled from a group of files ending in -context.xml contained

in the /WEB-INF/spring/ directory. The child context for the Flex-specific setup would be built (by

convention) from /WEB-INF/flex-servlet.xml, and the context for the Spring MVC controllers would be built

from /WEB-INF/spring-mvc-servlet.xml. This approach provides a nice separation of concerns and will allow

Spring 2.5+ annotated controllers to work using their default configuration.

An alternate approach is to keep things consolidated under one DispatcherServlet context. The down-side to

this approach is that it requires some additional manual configuration, and you have to modify your mapping

approach accordingly, such as mapping /spring/* to the DispatcherServlet, mapping /messagebroker/* to

the Spring-managed MessageBroker via the mapping XML namespace config tag, and modifying any BlazeDS

channel definitions accordingly. You would override the default mapping strategy of the message-broker tag

as follows:

<flex:message-broker>

<flex:mapping pattern="/messagebroker/*" />

</flex:message-broker>

and you would have to account for the /spring/* mapping in your BlazeDS channel definitions. For example:

<channel-definition id="my-amf" class="mx.messaging.channels.AMFChannel">

<endpoint url="http://{server.name}:{server.port}/{context.root}/spring/messagebroker/amf"

class="flex.messaging.endpoints.AMFEndpoint"/>

<polling-enabled>false</polling-enabled>

</properties>

</channel-definition>

Configuring and Using the BlazeDS MessageBroker with

Version 1.5.0.RELEASE 5

剩余36页未读，继续阅读

weishanxiao

粉丝: 9
资源: 8

Spring Flex 1.5配置指南：整合BlazeDS与Spring的详细教程

SpringFlex框架搭建

spring xml配置文件

springconfig 配置文件参数说明

spring boot配置文件

spring的配置文件

Spring Boot配置文件是什么

springcloud配置文件优先级

springcloud配置文件怎么配置，每个标签代表啥意思

Spring配置文件是什么

spring aop配置文件表头

spring bean配置xml文件

Spring aop 配置文件头部

JAVA代码读取spring配置文件_读取spring配置文件的方法(spring读取资源文件)

spring boot 配置文件redis集群

Spring配置文件在哪儿

获取Spring Boot配置文件参数。

java配置文件放置到jar外_Spring Boot配置文件放在jar外部

Spring 配置文件在哪

eclipse创建spring配置文件

springcloud配置中心

最新资源