Currently, a tool/service provider needs to provide their own implementation for parsing an XML document (or properties file) and getting the email template/associated metadata checking if the template needs to be updated and then calling the ETS to update it. This needs to be done for each template that the tool provides, and for every tool that uses the ETS, similar code needs to be duplicated.
I propose a method to provide the list of templates files via some sort of configuration, whether that be via a list property of a Spring bean or some other way. Then, then ETS would handle the reading of the XML template, checking if it needs to be updated, and updating the database. This centralises and consolidates where the parsing/loading/updating occurs.
The templates would need to be standardised, as per