I’m currently working on a project integrating the Openfire server with a custom webapp’s database and using a custom authentication provider. Then today I began getting errors and when looking to try and see what was offending in my conf/openfire.xml I found that openfire had unilaterally edited the file and stripped out almost all of my customizations, all of which had been working perfectly less than 24 hours previously.
Is there a way to prevent unprompted changes to conf/openfire.xml, or to have Openfire first create a backup copy (openfire.xml.bakXXXX, etc) when doing so?
Specifically, the error that led to this happening was
“Unable to load JDBC driver: Null
although various other errors that I have encountered trying to find the root issue have also led to this behavior.
Additionally, as long as I’m mentioning the configuration file, I don’t suppose there’s some way to force the configuration values to take precedence over those stored in SQL.