开源ESB阵营

图片：
图片：
图片：
图片：
图片：
图片：
图片：
图片：
图片：
图片：
图片：
图片：
图片：
图片：

开源ESB阵营，助推开源EAI、SOA的解决方案：
Mule: http://mule.mulesource.org/
ServiceMix: http://www.servicemix.org
开源ESB－－－MULE
1、简介：
Mule是技术领先的开源ESB与集成平台，它是一个可扩展的、高性能的分布式对象代理，通过分离传输与消息的技术实现对应用与服务接口的无缝处理，它是轻量级的消息处理框架，用来部署你的商业组件，在同一机制下（common messaging bus），负责透明的处理所有组件之间的交互，用JMS或其它消息服务实现消息通讯，BUS是共享消息通道。
2、关键特征：
  * J2EE 1.4 Enterprise Service Bus (ESB) and Messaging broker
  * Pluggable connectivity such as JMS (1.0.2b and 1.1), VM (embedded), JDBC, TCP, UDP, multicast, http, servlet, SMTP, POP3, file, XMPP.
  * JBI Integration.
  * Orchestration（聚集） of services using WS-BPEL（ BPEL is an XML language for describing business process behavior based on Web services） and Mule components and routers.
  * Support for asynchronous, synchronous and request-response event processing over any transport.
  * Web Services using XFire (STaX-based) Axis or Glue.
  * Flexible deployment including Client/Server, Peer-to-Peer, ESB and Enterprise Service Network.
  * Declarative and Programmatic transaction support including XA support.
  * End-to-End support for routing, transport and transformation of events.
  * Spring framework Integration. Can be used as the ESB container and Mule can be easily embedded into Spring applications.
  * Highly scalable enterprise server using the SEDA processing model.
  * REST API to provide technology agnostic and language neutral web based access to Mule Events
  * Powerful event routing based on patterns in the popular EIP book.
  * Dynamic, declarative, content-based and rule-based routing options.
  * Non-Intrusive approach. Any object can be managed by the ESB container.
  * Powerful Application Integration framework
  * Fully extensible development model
3、技术定位：商业组件的异构性、集成性、松耦合、健壮性、框架无关性、
  Mule fills a void in enterprise java development where an application requires complex interactions with a variety of systems on a variety of platforms. Mule makes light work of wiring these systems together in a robust decoupled environment and provides the necessary support to route, transport and transform data to and from these systems.
4、技术目标：
The goals of the Mule project and Universal Message Objects have been heard before a thousand times although not necessarily delivered together (or even delivered!) -

  * Scalable Enterprise Service Bus framework that should handle most of the complexities of systems integration.
  * Easy to use, yet powerful server that can operate over complex topologies.
  * Simple Autonomous component development and deployment
  * Code reuse. If all components are self-contained, independent units of work they can be plugged into any other system
  * Rapid time to market. Using Mule will provide time-saving features and functionality and should certainly not result in any development or maintenance overhead
  * Flexible a powerful configuration that should be easy to manage over a distributed environment.
When the Mule project started there seems to be a gap in the market for a simple and lightweight way to write components that do something to data without needing to worry about the sender or recipient of the data, the format of the data or the technology being used to send/receive the data. I emphasis simple because although many brokering and integration technologies offer ways of connecting to disparate data sources, you often have to do extra coding to get it to behave the way you want and to deliver the data where you want it to go. Mule allows you to quickly develop components and then change the way they behave through configuration instead of coding.