You are viewing a plain text version of this content. The canonical link for it is here.
Posted to wss4j-dev@ws.apache.org by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org> on 2008/09/26 18:39:44 UTC
[jira] Closed: (WSS-129) Couple places where "cause" of
WSSecurityException not set
[ https://issues.apache.org/jira/browse/WSS-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Colm O hEigeartaigh closed WSS-129.
-----------------------------------
> Couple places where "cause" of WSSecurityException not set
> ----------------------------------------------------------
>
> Key: WSS-129
> URL: https://issues.apache.org/jira/browse/WSS-129
> Project: WSS4J
> Issue Type: Bug
> Affects Versions: 1.5.5
> Reporter: Daniel Kulp
> Assignee: Colm O hEigeartaigh
> Fix For: 1.5.5
>
>
> There are a bunch of places in wss4j where exception thrown from xml-sec or saml or others are caught and then a WSSecurityException is thrown, but the original exception is not set as the cause so the real details are lost.
> Examples:
> WSSecSignatureSAML line 299, line 307
> WSConfig line 386, 419
> EncryptionAction line 65
> SAMLTokenSignedAction line 105
> etc....
> That can make debugging things quite a bit harder.
--
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