Modules Reference
| Mule runtime engine version 3.8 reached its End of Life on November 16, 2021. For more information, contact your Customer Success Manager to determine how to migrate to the latest Mule version. |
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 modules.
| Module | Description |
|---|---|
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. |
|
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. |
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). |