[jira] [Updated] (AXIOM-459) WS Security header is not being serialized when header element is not instance of org.apache.axiom.soap.SOAPHeader

2014-07-09 Thread Detelin Hadzhiev (JIRA)
[ https://issues.apache.org/jira/browse/AXIOM-459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Detelin Hadzhiev updated AXIOM-459: --- Description: Currently wss4j using DOM to produce WS security headers. When it is combined

[jira] [Commented] (AXIOM-459) WS Security header is not being serialized when header element is not instance of org.apache.axiom.soap.SOAPHeader

2014-07-09 Thread Detelin Hadzhiev (JIRA)
[ https://issues.apache.org/jira/browse/AXIOM-459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14055942#comment-14055942 ] Detelin Hadzhiev commented on AXIOM-459: Hi Veithen, There is some corner case when

[jira] [Commented] (AXIOM-459) WS Security header is not being serialized when header element is not instance of org.apache.axiom.soap.SOAPHeader

2014-07-09 Thread Andreas Veithen (JIRA)
[ https://issues.apache.org/jira/browse/AXIOM-459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14055945#comment-14055945 ] Andreas Veithen commented on AXIOM-459: --- What is the Rampart version? WS Security

[jira] [Commented] (AXIOM-459) WS Security header is not being serialized when header element is not instance of org.apache.axiom.soap.SOAPHeader

2014-07-09 Thread Detelin Hadzhiev (JIRA)
[ https://issues.apache.org/jira/browse/AXIOM-459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14055949#comment-14055949 ] Detelin Hadzhiev commented on AXIOM-459: Rampart version is 1.6.2. WS Security

Re: Apache Rampart test failure with wss4j 1.6.5 and later

2014-07-09 Thread Colm O hEigeartaigh
Thanks for the investigation. It turns out Maven 3.0.x is required to build Rampart. I've merged a fix for this issue in WSS4J, where we don't store the token Id if it is an empty String. IMO Rampart should also be fixed. Colm. On Tue, Jul 8, 2014 at 6:03 PM, detelinyorda...@gmail.com wrote:

Re: Apache Rampart test failure with wss4j 1.6.5 and later

2014-07-09 Thread detelinyordanov
I can open a defect in Rampart, but I'm not sure what should be the proposed change there - I was thinking that it can check for empty id tag and skip the result, but if wss4j does not generate results with empty id anymore, this will not be required. Rampart uses the following code to identify

Re: Apache Rampart test failure with wss4j 1.6.5 and later

2014-07-09 Thread Colm O hEigeartaigh
Well the thing is that WSS4J 1.6.16 was just released, and so the next release won't happen for a couple of months probably. So if you want to see a Rampart release before then, you could just submit a patch to check that the Id isn't empty. Colm. On Wed, Jul 9, 2014 at 1:32 PM,

RE: Apache Rampart test failure with wss4j 1.6.5 and later

2014-07-09 Thread Martin Gainty
Date: Wed, 9 Jul 2014 14:23:47 +0100 Subject: Re: Apache Rampart test failure with wss4j 1.6.5 and later From: cohei...@apache.org To: detelinyorda...@gmail.com CC: dev@ws.apache.org Well the thing is that WSS4J 1.6.16 was just released, and so the next release won't happen for a couple of

[XmlSchema 2.0] Project Status?

2014-07-09 Thread Michael Pigott
Hello Apache Web Services Developers, Last week I filed and provided a fix for https://issues.apache.org/jira/browse/XMLSCHEMA-33 (uploading the diff.zip yesterday). However, I haven't seen much traction on the JIRA ticket, and I am not sure who to reach out to. No lead developer is

Build failed in Jenkins: ws-axiom-trunk » Axiom #1854

2014-07-09 Thread Apache Jenkins Server
See https://builds.apache.org/job/ws-axiom-trunk/org.apache.ws.commons.axiom$axiom/1854/changes Changes: [veithen] Also rename the testsuites folder to testing. For some reasonm my SVN client didn't allow me to do that at the same time as the change in r1609259.

Build failed in Jenkins: ws-axiom-trunk #1854

2014-07-09 Thread Apache Jenkins Server
See https://builds.apache.org/job/ws-axiom-trunk/1854/changes Changes: [veithen] Set svn:ignore for Eclipse. [veithen] Also rename the testsuites folder to testing. For some reasonm my SVN client didn't allow me to do that at the same time as the change in r1609259. [veithen] Renamed the

Re: Apache Rampart test failure with wss4j 1.6.5 and later

2014-07-09 Thread detelinyordanov
Hi Martin, I think that the code you are referring to is in SymmetricBindingBuilder and it indeed checks if the Id is empty. However, the one in RampartUtil.getRequestEncryptedKeyId() does not do so. The fix is to add a check for empty Id there as well: Index:

Jenkins build is back to normal : ws-axiom-trunk » Axiom #1856

2014-07-09 Thread Apache Jenkins Server
See https://builds.apache.org/job/ws-axiom-trunk/org.apache.ws.commons.axiom$axiom/1856/ - To unsubscribe, e-mail: dev-unsubscr...@ws.apache.org For additional commands, e-mail: dev-h...@ws.apache.org

Build failed in Jenkins: ws-axiom-trunk #1857

2014-07-09 Thread Apache Jenkins Server
See https://builds.apache.org/job/ws-axiom-trunk/1857/changes Changes: [veithen] Added a SAAJ test case for the method that causes problems in the current Axis2 trunk. -- [...truncated 8497 lines...] Received 0 blocks and 2253 bytes Compression is 0.0%

Build failed in Jenkins: ws-axiom-trunk » Axiom DOM #1857

2014-07-09 Thread Apache Jenkins Server
See https://builds.apache.org/job/ws-axiom-trunk/org.apache.ws.commons.axiom$axiom-dom/1857/ -- [...truncated 113 lines...] [INFO] --- gmaven-plugin:1.2:execute (initialize) @ axiom-dom --- [INFO] [INFO] ---

RE: Apache Rampart test failure with wss4j 1.6.5 and later

2014-07-09 Thread Martin Gainty
Date: Wed, 9 Jul 2014 22:48:36 +0300 Subject: Re: Apache Rampart test failure with wss4j 1.6.5 and later From: detelinyorda...@gmail.com To: mgai...@hotmail.com CC: dev@ws.apache.org Hi Martin, I think that the code you are referring to is in SymmetricBindingBuilder and it indeed checks if