Currently the velocity.properties contains slots that need to be substituted to generate a path to the Velocity templates:
file.resource.loader.path = [PKI_INSTANCE_PATH]/[PKI_WEBAPPS_NAME]/[PKI_SUBSYSTEM_TYPE]
Since the templates do not contain configurable content, they don't actually need to be deployed into the instance directory. They can remain in the installation directory, i.e. /usr/share/pki/<subsystem>/webapps/<subsystem>. This way the velocity.properties can be deployed without customization.
An upgrade script will be needed to modify existing deployments.
If template customization is needed in the future, the templates can be organized as themes:
/usr/share/pki/templates + default + theme1 + theme2
The code then will be modified to include the theme name, for example CMS.getTemplate(theme+"/admin/console/config/wizard.vm").
attachment pki-edewata-0363-1-Replaced-Velocity-template-path.patch
[06/04/2014] - Moving to Milestone 10.2.3 due to schedule restrictions.
Per Dogtag 10.2.X meeting of 01/14/2015:
Rename ticket to remove velocity files.
Per Dogtag 10.2.X meeting of 01/14/2015: Milestone 10.3
Metadata Update from @edewata: - Issue set to the milestone: UNTRIAGED
Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.
This issue has been cloned to GitHub and is available here: https://github.com/dogtagpki/pki/issues/1319
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Metadata Update from @dmoluguw: - Issue close_status updated to: migrated - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.