Complete the spawn()/respawn()/destroy() methods for the 'configuration.py' scriptlet (and all associated general helper classes/methods)
CONSIDERATION: For spawn()/respawn(), this scriptlet may merely invoke a new Java configuration client which communicates with the new Installation Servlet.
The following ticket has been closed as a duplicate of this ticket:
Ticket #158: Installer -- Write connecting code from python to installation servlet. Code needs to be written to take the values gathered in the python installer, launch the java config client - and populate the relevant data objects. And report the corresponding results.
This ticket has been addressed by the following check-in:
commit 0ce6c97e4fe0e36786b78c273833b8f1dfbc12b4 Author: Matthew Harmsen mharmsen@redhat.com Date: Tue Jul 3 17:52:33 2012 -0700
PKI Deployment Scriptlets
- Integration of Tomcat 7 - Introduction of dependency upon tomcatjss 7.0 - Removal of http filtering configuration mechanisms - Introduction of additional slot substitution to support revised filesystem layout - Addition of 'pkiuser' uid:gid creation methods - Inclusion of per instance '*.profile' files - Introduction of configurable 'configurationRoot' parameter - Introduction of default configuration of 'log4j' mechanism (alee) - Modify web.xml to use new Application classes to bootstrap servers (alee) - Introduction of "Wrapper" logic to support Tomcat 6 --> Tomcat 7 API change (jmagne) - Added jython helper function to allow attaching a remote java debugger (e. g. - eclipse)
Metadata Update from @mharmsen: - Issue assigned to mharmsen - Issue set to the milestone: Dogtag 10.0 Alpha
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/709
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.