[jira] [Commented] (WSS-231) There is an issue with the position of the Timestamp element in the Security header when using WSS4J calling .NET Web Services with WS-Security.

2012-10-15 Thread Colm O hEigeartaigh (JIRA)
[ https://issues.apache.org/jira/browse/WSS-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13476016#comment-13476016 ] Colm O hEigeartaigh commented on WSS-231: - If you want me to help you, you'll need

[jira] [Commented] (WSS-231) There is an issue with the position of the Timestamp element in the Security header when using WSS4J calling .NET Web Services with WS-Security.

2012-10-12 Thread nag (JIRA)
[ https://issues.apache.org/jira/browse/WSS-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13475245#comment-13475245 ] nag commented on WSS-231: - If I have two secured elements like this ,I get error .

[jira] [Commented] (WSS-231) There is an issue with the position of the Timestamp element in the Security header when using WSS4J calling .NET Web Services with WS-Security.

2012-10-08 Thread Colm O hEigeartaigh (JIRA)
[ https://issues.apache.org/jira/browse/WSS-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13471472#comment-13471472 ] Colm O hEigeartaigh commented on WSS-231: - Any update on this? I'll release 1.5.13

[jira] [Commented] (WSS-231) There is an issue with the position of the Timestamp element in the Security header when using WSS4J calling .NET Web Services with WS-Security.

2012-10-01 Thread Colm O hEigeartaigh (JIRA)
[ https://issues.apache.org/jira/browse/WSS-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13466722#comment-13466722 ] Colm O hEigeartaigh commented on WSS-231: - Yes the change is committed. What web

[jira] [Commented] (WSS-231) There is an issue with the position of the Timestamp element in the Security header when using WSS4J calling .NET Web Services with WS-Security.

2012-09-29 Thread nag (JIRA)
[ https://issues.apache.org/jira/browse/WSS-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13466279#comment-13466279 ] nag commented on WSS-231: - Hi Colm, I have tried using 1.6.8-SNAPSHOT and still get same error as

[jira] [Commented] (WSS-231) There is an issue with the position of the Timestamp element in the Security header when using WSS4J calling .NET Web Services with WS-Security.

2012-09-29 Thread nag (JIRA)
[ https://issues.apache.org/jira/browse/WSS-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13466321#comment-13466321 ] nag commented on WSS-231: - Also wsse:Security /BinarySecurityToken is getting inserted before

[jira] [Commented] (WSS-231) There is an issue with the position of the Timestamp element in the Security header when using WSS4J calling .NET Web Services with WS-Security.

2012-09-17 Thread Colm O hEigeartaigh (JIRA)
[ https://issues.apache.org/jira/browse/WSS-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13456888#comment-13456888 ] Colm O hEigeartaigh commented on WSS-231: - By the end of the month. Colm.

[jira] [Commented] (WSS-231) There is an issue with the position of the Timestamp element in the Security header when using WSS4J calling .NET Web Services with WS-Security.

2012-09-11 Thread nag (JIRA)
[ https://issues.apache.org/jira/browse/WSS-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13453412#comment-13453412 ] nag commented on WSS-231: - We are currently stuck with this issue? when 1.5.13 will be released?

[jira] [Commented] (WSS-231) There is an issue with the position of the Timestamp element in the Security header when using WSS4J calling .NET Web Services with WS-Security.

2012-09-10 Thread nag (JIRA)
[ https://issues.apache.org/jira/browse/WSS-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13452470#comment-13452470 ] nag commented on WSS-231: - when 1.5.13 will be released? Thanks There is an

[jira] [Commented] (WSS-231) There is an issue with the position of the Timestamp element in the Security header when using WSS4J calling .NET Web Services with WS-Security.

2012-09-06 Thread Colm O hEigeartaigh (JIRA)
[ https://issues.apache.org/jira/browse/WSS-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13449690#comment-13449690 ] Colm O hEigeartaigh commented on WSS-231: - It will be fixed for 1.5.13. Colm.

[jira] [Commented] (WSS-231) There is an issue with the position of the Timestamp element in the Security header when using WSS4J calling .NET Web Services with WS-Security.

2012-09-05 Thread nag (JIRA)
[ https://issues.apache.org/jira/browse/WSS-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13448738#comment-13448738 ] nag commented on WSS-231: - Hi Colm, When you are going to release 1.6.8 version? Thanks

[jira] [Commented] (WSS-231) There is an issue with the position of the Timestamp element in the Security header when using WSS4J calling .NET Web Services with WS-Security.

2012-09-05 Thread nag (JIRA)
[ https://issues.apache.org/jira/browse/WSS-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13448764#comment-13448764 ] nag commented on WSS-231: - When I switch the actions to Signature Timestamp I am getting this error?

[jira] [Commented] (WSS-231) There is an issue with the position of the Timestamp element in the Security header when using WSS4J calling .NET Web Services with WS-Security.

2012-09-05 Thread Colm O hEigeartaigh (JIRA)
[ https://issues.apache.org/jira/browse/WSS-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13448766#comment-13448766 ] Colm O hEigeartaigh commented on WSS-231: - It doesn't work prior to the fix I have

[jira] [Commented] (WSS-231) There is an issue with the position of the Timestamp element in the Security header when using WSS4J calling .NET Web Services with WS-Security.

2012-09-05 Thread nag (JIRA)
[ https://issues.apache.org/jira/browse/WSS-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13448775#comment-13448775 ] nag commented on WSS-231: - Is there any temporary work around ? I need to complete my project to cal

[jira] [Commented] (WSS-231) There is an issue with the position of the Timestamp element in the Security header when using WSS4J calling .NET Web Services with WS-Security.

2012-09-05 Thread Colm O hEigeartaigh (JIRA)
[ https://issues.apache.org/jira/browse/WSS-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13448779#comment-13448779 ] Colm O hEigeartaigh commented on WSS-231: - You could switch to using WSS4J

[jira] [Commented] (WSS-231) There is an issue with the position of the Timestamp element in the Security header when using WSS4J calling .NET Web Services with WS-Security.

2012-09-05 Thread nag (JIRA)
[ https://issues.apache.org/jira/browse/WSS-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13448792#comment-13448792 ] nag commented on WSS-231: - thats only change in 1.6.8?I am using 1.5.9 today. Is it safe to use

[jira] [Commented] (WSS-231) There is an issue with the position of the Timestamp element in the Security header when using WSS4J calling .NET Web Services with WS-Security.

2012-09-05 Thread Colm O hEigeartaigh (JIRA)
[ https://issues.apache.org/jira/browse/WSS-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13448795#comment-13448795 ] Colm O hEigeartaigh commented on WSS-231: - There are huge changes in 1.6.x compared

[jira] [Commented] (WSS-231) There is an issue with the position of the Timestamp element in the Security header when using WSS4J calling .NET Web Services with WS-Security.

2012-04-10 Thread Raj Kumar (Commented) (JIRA)
[ https://issues.apache.org/jira/browse/WSS-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13250505#comment-13250505 ] Raj Kumar commented on WSS-231: --- Can someone show me how to do that reordering using a CXF

[jira] [Commented] (WSS-231) There is an issue with the position of the Timestamp element in the Security header when using WSS4J calling .NET Web Services with WS-Security.

2012-03-01 Thread Kevin T (Commented) (JIRA)
[ https://issues.apache.org/jira/browse/WSS-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13220440#comment-13220440 ] Kevin T commented on WSS-231: - Abd K, I am coming across this issue too. I went and got the

[jira] Commented: (WSS-231) There is an issue with the position of the Timestamp element in the Security header when using WSS4J calling .NET Web Services with WS-Security.

2011-02-18 Thread Abd K (JIRA)
[ https://issues.apache.org/jira/browse/WSS-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12996501#comment-12996501 ] Abd K commented on WSS-231: --- I've come across the same issue. Are there any plans to fix this?

[jira] Commented: (WSS-231) There is an issue with the position of the Timestamp element in the Security header when using WSS4J calling .NET Web Services with WS-Security.

2010-05-27 Thread Colm O hEigeartaigh (JIRA)
[ https://issues.apache.org/jira/browse/WSS-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12872174#action_12872174 ] Colm O hEigeartaigh commented on WSS-231: - I don't think it's possible to construct a

[jira] Commented: (WSS-231) There is an issue with the position of the Timestamp element in the Security header when using WSS4J calling .NET Web Services with WS-Security.

2010-05-20 Thread Colm O hEigeartaigh (JIRA)
[ https://issues.apache.org/jira/browse/WSS-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12869605#action_12869605 ] Colm O hEigeartaigh commented on WSS-231: - As Werner said, try reversing the action

[jira] Commented: (WSS-231) There is an issue with the position of the Timestamp element in the Security header when using WSS4J calling .NET Web Services with WS-Security.

2010-05-20 Thread Chris Weitner (JIRA)
[ https://issues.apache.org/jira/browse/WSS-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12869666#action_12869666 ] Chris Weitner commented on WSS-231: --- We are signing the Timestamp, so if the order is