Currently the subsystem web.xml contains slots that need to substituted during deployment in order to generate the value for cfgPath parameter:
<servlet> <servlet-name>...</servlet-name> <servlet-class>com.netscape.cms.servlet.base.CMSStartServlet</servlet-class> <init-param> <param-name>cfgPath</param-name> <param-value>[PKI_INSTANCE_PATH]/conf/[PKI_SUBSYSTEM_TYPE]/CS.cfg</param-value> </init-param> ... </servlet>
The value can actually be computed with this code:
ServletContext servletContext = config.getServletContext(); String instanceDir = System.getProperty("catalina.base"); String subsystem = servletContext.getContextPath().substring(1); String path = instanceDir + "/conf/" + subsystem + "/CS.cfg";
So the cfgPath can be removed from the web.xml. This way the web.xml no longer needs to be customized for each instance, allowing direct web application deployment in the future. See: http://pki.fedoraproject.org/wiki/Customization#Direct_Deployment
An upgrade script is needed to remove the cfgPath from existing web.xml.
master: 4c1ce953681c3cac9c6d0b4325a48ba66619f553
Metadata Update from @edewata: - Issue assigned to edewata - Issue set to the milestone: 10.2 - 03/14 (March)
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/1315
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.
Login to comment on this ticket.