[jira] Updated: (WSS-85) Better exception handling in the crypto (e.g. no e.printStackTrace())

["Colm O hEigeartaigh (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/WSS-85?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Colm O hEigeartaigh updated WSS-85:
-----------------------------------

    Fix Version/s: 1.5.5

> Better exception handling in the crypto (e.g. no e.printStackTrace())
> ---------------------------------------------------------------------
>
>                 Key: WSS-85
>                 URL: https://issues.apache.org/jira/browse/WSS-85
>             Project: WSS4J
>          Issue Type: Improvement
>            Reporter: Christof Soehngen
>            Assignee: Nandana Mihindukulasooriya
>             Fix For: 1.5.5
>
>
> When loading a crypto, the constructor tries to load the keystore mentioned in the properties.
> If any exception happens loading the keystore (e.g. file not found, wrong password, ...), the exception is printed out via e.printStracktrace() and a new, more general exception is thrown (without the details of the original exception).
> In environments, where error handling is done mainly via log files and the stack traces contained within, there is no way to figure out, what specifically went wrong.
> It would be desirable to hand the original exceptions with details (IOException, ...)  to the caller, so that he can decide where to write the information.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org