Spring BlazeDS 集成指南：官方文档解析

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

"Spring Flex BlazeDS 集成官方文档提供了关于如何将Spring框架与Adobe BlazeDS相结合的详细指南。这份文档适用于版本1.5.2.RELEASE，由Jeremy Grelle（来自SpringSource）在2011年11月发布。文档允许非商业复制和分发，但需保留版权信息。 Spring BlazeDS Integration 是一个用于构建富互联网应用程序(RIA)的解决方案，它使Java开发者能够利用Spring框架的强大功能与BlazeDS的实时通信能力。BlazeDS是Adobe提供的一种服务器端技术，它支持Flex客户端与Java后端服务之间的数据交互。文档首先介绍了集成背景，说明了Spring BlazeDS Integration的主要依赖版本，包括Spring框架和BlazeDS的最低版本要求。此外，还提到了某些可选功能可能需要的额外依赖版本。文档的这部分帮助开发者了解系统需求，确保项目顺利运行。配置和使用BlazeDS消息代理是文档的核心部分，包括以下子章节： 1. 引入：概述了Spring如何与BlazeDS的MessageBroker协同工作，提供了一种灵活的方式管理和调度消息。 2. 配置Spring Dispatcher Servlet：讲解如何配置Spring MVC的前端控制器，以便处理来自Flex客户端的请求。 3. 在Spring中配置MessageBroker：详述了如何在Spring应用上下文中定义和配置BlazeDS的消息代理。 4. 映射请求到MessageBroker：说明了如何将Flex客户端的请求映射到特定的服务端处理方法。 5. 与Spring MVC控制器一起使用Flex客户端：指导如何在Flex应用中同时使用Spring MVC控制器，实现前后端的无缝集成。 6. 使用Spring管理的Destination：解释了如何让Flex客户端与由Spring管理的后端bean进行交互。 7. 高级MessageBroker自定义：讨论了如何根据项目需求对消息代理进行更深入的定制。 8. 使用自定义异常转换器：展示了如何处理Flex客户端和服务器之间转换和传递异常的策略。 9. 使用自定义消息拦截器：这部分涵盖了自定义拦截器的使用，以在消息传递过程中添加额外的功能或日志记录。文档的2.9.1节进一步详细介绍了资源处理，这可能是关于如何处理Flex客户端与服务器之间交换的数据资源的细节。这份Spring Flex BlazeDS集成官方文档是开发人员在构建基于Spring和BlazeDS的RIA时不可或缺的参考，它涵盖了从基础配置到高级定制的所有关键步骤。通过遵循这些指南，开发者可以有效地利用Spring的灵活性和BlazeDS的实时通信能力，创建高效、健壮的Flex应用。"

<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.2.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.2.RELEASE 5

剩余36页未读，继续阅读

xiezhongju

粉丝: 0
资源: 1

Spring BlazeDS 集成指南：官方文档解析

Spring BlazeDS Integration Spring集成BlazeDS

spring-flex官方文档

Flex之BlazeDS文档

flex4.5+java+spring+blazeds通信

Flex BlazeDS与Java Spring集成配置详解

Spring BlazeDS 集成指南

Spring BlazeDS与Flex集成详解：构建高效通信架构

Flex+BlazeDS+Spring+Hibernate集成配置教程

Flex-Spring-JAVA-BLAZEDS.rar_Flex spring_flex_flex java

Spring Flex 配置文档

最新资源