You are viewing an older version of this topic. To go to a different version, use the version menu at the upper-right. +

Modules Reference

This topic relates to the most recent version of Mule ESB. To see the corresponding topic in a previous version of Mule ESB, click MULE2USER:UsingMuleModules[here].

Modules are similar to transports in that they provide pluggable functionality, configured via dedicated schema, but they differ in that there is no underlying transport to send or receive data. Following is a list of the default Mule ESB modules.

Module Description

Security via Acegi.

Support for consuming and creating Atom feeds.


Mule’s support for BPM allows you to send/receive messages to/from a running process. A message from Mule can start or advance a process, the message can be stored as a process variable, and a running process can send messages to any endpoint in your Mule application.

Mule 3.0 architectural changes bring much better support for CXF, meaning it can be used just like another pipe/filter element.

MuleClient and the remote dispatcher, giving simple access to the Mule server.

Security via JAAS.

JBoss transaction support.

JBoss jBPM is an open source BPMS and is well-integrated with Mule. One advantage of jBPM is that it is embedded directly in the Mule runtime, allowing for faster performance.

Support for RESTful web services built using Jersey.

JSON data and binding support.

Mule agents for server management using JMX.

OGNL Module

Provides a filter using OGNL expressions. For details, see Using OGNL Expressions.

Security via PGP.

SAML Module *Enterprise Edition*

Provides authentication and authorization capabilities to Mule based on the SAML standard. (As of Mule enterprise edition 2.2.3)

Support for consuming RSS feeds

Interface between Mule and scripting languages (currently groovy).

Extensions for using the Spring framework with Mule.

A very fast streaming XPath router and filter.

XML based utilities (mainly filters and routers).