We think of two solutions for this issue:
- at startup first, delete all the datasources from JBoss using the Management API, then create them again based on the application configuration
Instead of that, why not check the "presence" of your datasource using the Management API and if it's present, then skip the creation part.
- don't persist the changes made by the Management API
No that's not possible.
Thanks for your reply Jaikiran.
I'm afraid that this would not solve our problem.
We have to assume that while the application/server is down the configuration file of the application can be altered.
At startup of the server this assumption would force us to first delete all the datasources (and other configured components) and then recreate them based on the settings in the application configuration.
This is such a tremendous overhead and would significantly slow down the lightning boot speed of our Jboss server that we are hoping there is an alternative. Has anyone an idea on how to solve this?
What is it the design reason to not have the option to reflect the configuration changes only in the runtime?
Thanks a lot.