One of the most common issues in reusing existing applications is bridging between different messaging systems. Bridging between different messaging systems involves solving two problems. One is that messaging systems from different vendors typically use different transport protocols and wire formats. The second is that the structure of the messages used by different applications are often dissimilar. Solving these problems could require reimplementing one or both of the existing applications. However, the Celtix Enterprise router can address both of these problems by providing a bridge between different transports and a means of converting messages from one format to another.

The router performs the needed processing based on the physical details of the endpoints in a route. For example if the inbound endpoint uses SOAP/HTTP and the outbound endpoint uses some proprietary XML format and an AMQP messaging system, a route can be deployed that will read in SOAP/HTTP requests, convert them into the XML format, if it is properly described in the outbound endpoint's contract, and place it on the AMQP destination used by the outbound endpoint.