Message Router Implementation is Configurable Too
Prev | Chapter 52. Configuration Changes in the Tigase Server 5.x | Next

## Message Router Implementation is Configurable Too

The Message router component was the only component which was fixed to the Tigase instance. In theory it could always be replaced but in practise there was no way of doing it as that was the first element loaded at the server startup time.

Now the Tigase message router implementation can be easily replaced to and it can be made a configurable option if needed.

At the server startup time the code creates configurator and calls method: getMessageRouterClassName() which by default returns class: tigase.server.MessageRouter. You can extend the configurator and provide any different class name instead which implements required interfaces. You can even make it configurable. It is no longer a fixed thing for the server instance.

Prev | Up | Next
Going Further | Home | Chapter 53. Advanced Message Processing - AMP XEP-0079