[JIRA] Updated: (MDA-66) should be possible to have CLI termination without a stack dump

Ian Young (JIRA) noreply at shibboleth.net
Mon Oct 8 05:05:22 EDT 2012


     [ https://issues.shibboleth.net/jira/browse/MDA-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ian Young updated MDA-66:
-------------------------

    Assignee: Ian Young  (was: Chad La Joie)

> should be possible to have CLI termination without a stack dump
> ---------------------------------------------------------------
>
>                 Key: MDA-66
>                 URL: https://issues.shibboleth.net/jira/browse/MDA-66
>             Project: Metadata Aggregator
>          Issue Type: Improvement
>          Components: Command Line
>    Affects Versions: 0.6.1
>            Reporter: Ian Young
>            Assignee: Ian Young
>
> I'd like to have a way of terminating the CLI by throwing an exception without ending up with a stack trace.
> At the moment, I throw a custom subclass of StageProcessingException called ...TerminationException, which is handled by the CLI like this:
> } catch (Exception e) { log.error("Error processing information", e); System.exit(1); }
> This results in a stack dump, which isn't very "CLI-ish" to me. I think what I'd prefer would be for the CLI to know about a specific Exception of its own that I could throw to get the log.error and System.exit but without the stack dump. It would probably also have to be a subclass of StageProcessingException in order to propagate through the rest of the system properly. I suggest net.shibboleth.metadata.pipeline.TerminationException.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the commits mailing list