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 "Daniel Kulp (JIRA)" <ji...@apache.org> on 2008/06/20 17:05:45 UTC
[jira] Created: (WSS-129) Couple places where "cause" of
WSSecurityException not set
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: Ruchith Udayanga Fernando
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
[jira] Closed: (WSS-129) Couple places where "cause" of
WSSecurityException not set
Posted by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org>.
[ 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
[jira] Updated: (WSS-129) Couple places where "cause" of
WSSecurityException not set
Posted by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WSS-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Colm O hEigeartaigh updated WSS-129:
------------------------------------
Fix Version/s: 1.5.5
> 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: Ruchith Udayanga Fernando
> 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
[jira] Commented: (WSS-129) Couple places where "cause" of
WSSecurityException not set
Posted by "Werner Dittmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WSS-129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12635105#action_12635105 ]
Werner Dittmann commented on WSS-129:
-------------------------------------
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
> 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
[jira] Commented: (WSS-129) Couple places where "cause" of
WSSecurityException not set
Posted by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WSS-129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12635332#action_12635332 ]
Colm O hEigeartaigh commented on WSS-129:
-----------------------------------------
Hrm, that never occurred to me. IMO it's reasonable to drop support for JDK 1.3 at this stage. If there are objections though, I can roll back the changes.
> 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
RE: [jira] Resolved: (WSS-129) Couple places where "cause" of WSSecurityException not set
Posted by "O hEigeartaigh, Colm" <Co...@iona.com>.
I tried to compile the source with JDK "1.3.1_09", jce-jdk13-141.jar and
j2ee.jar. Leaving aside the exception propagation changes, I get the
following errors.
Missing classes:
java.security.cert.CertPath
java.security.cert.CertPathValidator
java.security.cert.CertPathValidatorException
java.security.cert.PKIXParameters
Two protected access problems with:
java.util.Calendar#getTimeInMillis()
java.util.Calendar#setTimeInMillis(long)
I see someone else had similar questions back in 2004:
http://osdir.com/ml/apache.webservices.fx.devel/2004-12/msg00093.html
My conclusion is that JDK 1.3 is not supported at all for WSS4J 1.5.x.
Colm.
-----Original Message-----
From: Fred Dushin [mailto:fadushin@apache.org]
Sent: 29 September 2008 11:37
To: wss4j-dev
Subject: Re: [jira] Resolved: (WSS-129) Couple places where "cause" of
WSSecurityException not set
This could be a problem. Does Axis support 1.3?
On Sep 27, 2008, at 2:19 AM, Werner Dittmann wrote:
> 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.pl
ugin.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: wss4j-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: wss4j-dev-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org
----------------------------
IONA Technologies PLC (registered in Ireland)
Registered Number: 171387
Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland
---------------------------------------------------------------------
To unsubscribe, e-mail: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org
Re: [jira] Resolved: (WSS-129) Couple places where "cause" of
WSSecurityException not set
Posted by Fred Dushin <fa...@apache.org>.
This could be a problem. Does Axis support 1.3?
On Sep 27, 2008, at 2:19 AM, Werner Dittmann wrote:
> 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: wss4j-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: wss4j-dev-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org
Re: [jira] Resolved: (WSS-129) Couple places where "cause" of WSSecurityException
not set
Posted by Werner Dittmann <We...@t-online.de>.
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: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org
[jira] Resolved: (WSS-129) Couple places where "cause" of
WSSecurityException not set
Posted by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org>.
[ 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.
--
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
[jira] Assigned: (WSS-129) Couple places where "cause" of
WSSecurityException not set
Posted by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WSS-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Colm O hEigeartaigh reassigned WSS-129:
---------------------------------------
Assignee: Colm O hEigeartaigh (was: Ruchith Udayanga Fernando)
> 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