When refactoring the DataSource configuration and management, I learned that if the DataSource changes , Activiti does not pick it up because it instantiates the ProcessConfiguration during activation, and is never re-activated. There may be a way to create a DataSource proxy that delegates to the DataSourceService for every internal DataSource use. More research is necessary.
Goal: To be able to edit datasource.jdbc-default.json and have Activiti continue to operate. Presently, you get a bunch of "datasource has been closed" stack traces.