Because of these fixes WSS4J is no longer compatible with Java 1.3
because that (old) version did not support this exception propagation.
An update to the README, version info etc might be necessary to point out
that upcoming versions of WSS4J do not support JDK 1.3 any more.
Regards,
Werner
Colm O hEigeartaigh (JIRA) schrieb:
[
https://issues.apache.org/jira/browse/WSS-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colm O hEigeartaigh resolved WSS-129.
-------------------------------------
Resolution: Fixed
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.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
