The model element is a wrapper for all of the configuration required by a deployed router. It contains one or more mule-descriptor child elements that each describe a single route. It also contains configuration for any components that participate in a chained route. The model has a single attribute called name. The name attribute can be set to any string value.

The direct children of the model element are mule-descriptor elements. These elements define a single route. A route definition includes the definition of the inbound router and its endpoints, the UMO, and the outbound router and its endpoints. The mule-descriptor element has two attributes: name and implementation. Table 5.2, “Attributes of the mule-descriptor Element” describes the attributes.

The mule-descriptor element's children describe the endpoints involved in the route and the logic used to direct messages between them. There are two types of components involved in describing the routing logic: an inbound router and an outbound router. The mule-descriptor must have at least one inbound router definition.

Inbound routers are defined using an inbound-router element. These elements are wrappers for one or more endpoint definitions. Endpoints in the router context are the same as endpoints in the SOA context. They define a set of functionality and how it is exposed. Endpoints are defined using endpoint elements.

Outbound routers are defined using an outbound-router element. Outbound router definitions are similar to inbound routers with one important distinction. The endpoints of a an outbound router are wrapped by a router element. The router element specifies the class that implements the router functionality that determines how messages are delivered to the outbound endpoints.