Allow database used for MUC MAM to be configurable
Closed this issue · 1 comments
Openfire, as well as the Monitoring plugin, provides a database table where MUC messages are stored (this does not hold true for one-on-one messages, which are only stored in a database table provided by the Monitoring plugin).
The content of both tables is roughly equivalent, but is different in specific details (eg: with #133, PMs will only be available in the database-table provided by the Monitoring plugin).
Version 2.2.0 of the Monitoring plugin will switch from using the Openfire-provided table to the one provided by the Monitoring plugin. However, for specific use cases, it could be desirable to keep using the Openfire-provided table.
A configurable property should be introduced that can be used to define what table is to be used.
The property that will be used for this is conversation.database.use-openfire-tables - it takes a boolean value, and defaults to false