This allows us to create exceptions in TPS that will allow for the normal chaining of exceptions used by the printStackTrace routine. Right now EBaseClass has a constructor that takes another exception but only stores it away for its own use.
If we wanted to take advantage of system support for this we would call the constructor of "Exception" and give it incoming exception.
The change could be simple but we need to look at what the current class is doing with that incoming exception. We don't want it to conflict with system behavior should be enable system behavior.
This feature of course can be used by all the other subsystems as well since EBaseException is used everywhere.
Per CS/DS Meeting on 3/24/2014.
Nice to have and would be a candidate for 10.2.1. Will result in better way to diagnose errors.
Proposed Milestone: 10.2.2 (per CS Meeting of 09/17/2014)
Per Dogtag 10.2.X meeting of 01/14/2015: Milestone 10.2 Backlog
master:
Metadata Update from @jmagne: - Issue assigned to edewata - Issue set to the milestone: 10.2.2
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/1482
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.