| Andreas Veithen (JIRA) |
[jira] [Updated] (AXIOM-423) WSS4J fails when processing SAML Tokens since org.apache.axiom.om.impl.dom.NodeImpl has not implemented some required methods such as lookupNamespaceURI(), hence Rampart Trust module fails. |
Sat, 01 Sep, 08:38 |
| Andreas Veithen (JIRA) |
[jira] [Work started] (AXIOM-423) WSS4J fails when processing SAML Tokens since org.apache.axiom.om.impl.dom.NodeImpl has not implemented some required methods such as lookupNamespaceURI(), hence Rampart Trust module fails. |
Sat, 01 Sep, 08:38 |
|
[jira] [Commented] (AXIOM-423) WSS4J fails when processing SAML Tokens since org.apache.axiom.om.impl.dom.NodeImpl has not implemented some required methods such as lookupNamespaceURI(), hence Rampart Trust module fails. |
|
| Hudson (JIRA) |
[jira] [Commented] (AXIOM-423) WSS4J fails when processing SAML Tokens since org.apache.axiom.om.impl.dom.NodeImpl has not implemented some required methods such as lookupNamespaceURI(), hence Rampart Trust module fails. |
Sat, 01 Sep, 09:23 |
| Andreas Veithen (JIRA) |
[jira] [Commented] (AXIOM-423) WSS4J fails when processing SAML Tokens since org.apache.axiom.om.impl.dom.NodeImpl has not implemented some required methods such as lookupNamespaceURI(), hence Rampart Trust module fails. |
Sat, 01 Sep, 09:36 |
| Hudson (JIRA) |
[jira] [Commented] (AXIOM-423) WSS4J fails when processing SAML Tokens since org.apache.axiom.om.impl.dom.NodeImpl has not implemented some required methods such as lookupNamespaceURI(), hence Rampart Trust module fails. |
Sat, 01 Sep, 10:45 |
| Brian Reinhold (JIRA) |
[jira] [Commented] (AXIOM-423) WSS4J fails when processing SAML Tokens since org.apache.axiom.om.impl.dom.NodeImpl has not implemented some required methods such as lookupNamespaceURI(), hence Rampart Trust module fails. |
Sat, 01 Sep, 11:32 |
| Andreas Veithen (JIRA) |
[jira] [Commented] (AXIOM-423) WSS4J fails when processing SAML Tokens since org.apache.axiom.om.impl.dom.NodeImpl has not implemented some required methods such as lookupNamespaceURI(), hence Rampart Trust module fails. |
Sat, 01 Sep, 11:57 |
| Hudson (JIRA) |
[jira] [Commented] (AXIOM-423) WSS4J fails when processing SAML Tokens since org.apache.axiom.om.impl.dom.NodeImpl has not implemented some required methods such as lookupNamespaceURI(), hence Rampart Trust module fails. |
Sat, 01 Sep, 12:22 |
| Hudson (JIRA) |
[jira] [Commented] (AXIOM-423) WSS4J fails when processing SAML Tokens since org.apache.axiom.om.impl.dom.NodeImpl has not implemented some required methods such as lookupNamespaceURI(), hence Rampart Trust module fails. |
Sat, 01 Sep, 17:16 |
| Suresh Attanayake (JIRA) |
[jira] [Commented] (AXIOM-423) WSS4J fails when processing SAML Tokens since org.apache.axiom.om.impl.dom.NodeImpl has not implemented some required methods such as lookupNamespaceURI(), hence Rampart Trust module fails. |
Sat, 01 Sep, 19:05 |
| Hudson (JIRA) |
[jira] [Commented] (AXIOM-423) WSS4J fails when processing SAML Tokens since org.apache.axiom.om.impl.dom.NodeImpl has not implemented some required methods such as lookupNamespaceURI(), hence Rampart Trust module fails. |
Sun, 02 Sep, 09:31 |
| Hudson (JIRA) |
[jira] [Commented] (AXIOM-423) WSS4J fails when processing SAML Tokens since org.apache.axiom.om.impl.dom.NodeImpl has not implemented some required methods such as lookupNamespaceURI(), hence Rampart Trust module fails. |
Wed, 05 Sep, 19:56 |
| Hudson (JIRA) |
[jira] [Commented] (AXIOM-423) WSS4J fails when processing SAML Tokens since org.apache.axiom.om.impl.dom.NodeImpl has not implemented some required methods such as lookupNamespaceURI(), hence Rampart Trust module fails. |
Thu, 06 Sep, 08:31 |
| Hudson (JIRA) |
[jira] [Commented] (AXIOM-423) WSS4J fails when processing SAML Tokens since org.apache.axiom.om.impl.dom.NodeImpl has not implemented some required methods such as lookupNamespaceURI(), hence Rampart Trust module fails. |
Mon, 10 Sep, 08:26 |
| Sagara Gunathunga |
/www.apache.org/dist/ws/neethi/3.0.1 |
Sun, 02 Sep, 08:34 |
| Daniel Kulp |
Re: /www.apache.org/dist/ws/neethi/3.0.1 |
Thu, 06 Sep, 01:57 |
|
[jira] [Commented] (WSS-401) Concurrency issue in generating signature under high load |
|
| Colm O hEigeartaigh (JIRA) |
[jira] [Commented] (WSS-401) Concurrency issue in generating signature under high load |
Mon, 03 Sep, 13:31 |
| Hasini Gunasinghe (JIRA) |
[jira] [Commented] (WSS-401) Concurrency issue in generating signature under high load |
Wed, 05 Sep, 18:07 |
| Colm O hEigeartaigh (JIRA) |
[jira] [Commented] (WSS-401) Concurrency issue in generating signature under high load |
Mon, 17 Sep, 13:04 |
| Colm O hEigeartaigh (JIRA) |
[jira] [Commented] (WSS-401) Concurrency issue in generating signature under high load |
Mon, 24 Sep, 11:00 |
| Colm O hEigeartaigh (JIRA) |
[jira] [Commented] (WSS-402) Message not being signed correctly when using RSA (2048 bit ) certs |
Mon, 03 Sep, 13:33 |
| Apache Jenkins Server |
Jenkins build is back to normal : ws-axiom-trunk #1202 |
Tue, 04 Sep, 00:53 |
|
[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. |
|
| nag (JIRA) |
[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. |
Wed, 05 Sep, 01:38 |
| nag (JIRA) |
[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. |
Wed, 05 Sep, 13:54 |
| Colm O hEigeartaigh (JIRA) |
[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. |
Wed, 05 Sep, 14:08 |
| nag (JIRA) |
[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. |
Wed, 05 Sep, 14:14 |
| Colm O hEigeartaigh (JIRA) |
[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. |
Wed, 05 Sep, 14:16 |
| nag (JIRA) |
[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. |
Wed, 05 Sep, 14:30 |
| Colm O hEigeartaigh (JIRA) |
[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. |
Wed, 05 Sep, 14:34 |
| nag (JIRA) |
[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. |
Wed, 05 Sep, 14:45 |
| Colm O hEigeartaigh (JIRA) |
[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. |
Wed, 05 Sep, 14:49 |
| nag (JIRA) |
[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. |
Wed, 05 Sep, 15:58 |
| Colm O hEigeartaigh (JIRA) |
[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. |
Thu, 06 Sep, 14:01 |
| nag (JIRA) |
[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. |
Mon, 10 Sep, 21:37 |
| nag (JIRA) |
[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. |
Tue, 11 Sep, 21:04 |
| Colm O hEigeartaigh (JIRA) |
[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. |
Mon, 17 Sep, 08:47 |
| nag (JIRA) |
[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. |
Sat, 29 Sep, 18:10 |
| nag (JIRA) |
[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. |
Sat, 29 Sep, 21:30 |
| Apache Jenkins Server |
Build failed in Jenkins: neethi-trunk #641 |
Wed, 05 Sep, 01:40 |
| Apache Jenkins Server |
Jenkins build is back to normal : neethi-trunk #642 |
Wed, 05 Sep, 09:26 |
| Amila Suriarachchi |
Axiom Reads the whole input stream when applying the xpaths |
Wed, 05 Sep, 06:25 |
| Andreas Veithen |
Re: Axiom Reads the whole input stream when applying the xpaths |
Thu, 06 Sep, 08:30 |
| Hudson (JIRA) |
[jira] [Commented] (AXIOM-150) org.apache.axiom.om.impl.dom.DOMUtil#isValidChras(String) |
Wed, 05 Sep, 09:25 |
| Colm O hEigeartaigh (JIRA) |
[jira] [Assigned] (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. |
Wed, 05 Sep, 13:25 |
|
[jira] [Updated] (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. |
|
| Colm O hEigeartaigh (JIRA) |
[jira] [Updated] (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. |
Wed, 05 Sep, 13:25 |
| Colm O hEigeartaigh (JIRA) |
[jira] [Updated] (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. |
Thu, 06 Sep, 13:51 |
| Colm O hEigeartaigh (JIRA) |
[jira] [Resolved] (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. |
Wed, 05 Sep, 14:08 |
| Colm O hEigeartaigh (JIRA) |
[jira] [Resolved] (WSS-311) Streaming-WebService-Security-Framework contribution/donation |
Wed, 05 Sep, 14:10 |
| Colm O hEigeartaigh (JIRA) |
[jira] [Updated] (WSS-311) Streaming-WebService-Security-Framework contribution/donation |
Wed, 05 Sep, 14:10 |
| Colm O hEigeartaigh (JIRA) |
[jira] [Resolved] (WSS-328) Impossible to sign BST since 1.6.x |
Wed, 05 Sep, 14:10 |
|
Jenkins build is back to stable : wss4j-1.6 » Apache WSS4J #5 |
|
| Apache Jenkins Server |
Jenkins build is back to stable : wss4j-1.6 » Apache WSS4J #5 |
Wed, 05 Sep, 14:11 |
|
Jenkins build is back to stable : wss4j-1.6 #5 |
|
| Apache Jenkins Server |
Jenkins build is back to stable : wss4j-1.6 #5 |
Wed, 05 Sep, 14:11 |
| Colm O hEigeartaigh (JIRA) |
[jira] [Comment Edited] (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. |
Wed, 05 Sep, 14:34 |
| Andreas Veithen (JIRA) |
[jira] [Updated] (AXIOM-374) Behavior of OMFactory#createOMElement(QName [, OMContainer]) is inconsistent between LLOM and DOOM |
Wed, 05 Sep, 16:14 |
| Andreas Veithen (JIRA) |
[jira] [Updated] (AXIOM-404) Add a feature to detach a builder from the underlying stream |
Wed, 05 Sep, 16:14 |
| Andreas Veithen (JIRA) |
[jira] [Updated] (AXIOM-201) OMSourcedElement is always expanded when getXMLStreamReader is used on one of its ancestors |
Wed, 05 Sep, 16:14 |
| Andreas Veithen (JIRA) |
[jira] [Updated] (AXIOM-362) SOAPHeader examineAllHeaderBlocks throws ClassCastException |
Wed, 05 Sep, 16:16 |
| Andreas Veithen (JIRA) |
[jira] [Updated] (AXIOM-387) Deprecate getChildrenWithName and introduce a replacement method |
Wed, 05 Sep, 16:16 |
| Andreas Veithen (JIRA) |
[jira] [Updated] (AXIOM-432) Updating the last child is not correct unless we are replacing the last child |
Wed, 05 Sep, 16:16 |
| Andreas Veithen (JIRA) |
[jira] [Updated] (AXIOM-434) Base64 class doesn't throw exception for invalid input. |
Wed, 05 Sep, 16:18 |
| Andreas Veithen (JIRA) |
[jira] [Updated] (AXIOM-426) StAX dialect resolved as UnknownStAXDialect under JBoss AS 7.1 |
Wed, 05 Sep, 16:20 |
| Andreas Veithen (JIRA) |
[jira] [Updated] (AXIOM-431) SOAP envelopes created by ApplicationXMLBuilder lead to OMExeption during parse when imported via ElementHelper |
Wed, 05 Sep, 16:22 |
| Andreas Veithen (JIRA) |
[jira] [Resolved] (AXIOM-436) Axiom-api module: Many IllegalArgumentExceptions raised for unknown property configuration keys |
Wed, 05 Sep, 16:24 |
| Andreas Veithen (JIRA) |
[jira] [Updated] (AXIOM-418) Remove the dependency on JavaMail |
Wed, 05 Sep, 16:24 |
| Apache Jenkins Server |
Jenkins build is back to normal : ws-axiom-trunk #1208 |
Thu, 06 Sep, 08:30 |
| Colm O hEigeartaigh (JIRA) |
[jira] [Resolved] (WSS-360) Port BSP enforcer to streaming code. |
Thu, 06 Sep, 16:25 |
|
Re: WSS4J trunk |
|
| Andreas Veithen |
Re: WSS4J trunk |
Fri, 07 Sep, 06:46 |
| Marc Giger |
Re: WSS4J trunk |
Fri, 07 Sep, 07:26 |
| Rajika Kumarasiri |
[VFS] FTPS problem |
Fri, 07 Sep, 09:59 |
| Rajika Kumarasiri |
Re: [VFS] FTPS problem |
Fri, 07 Sep, 10:02 |
| Gary Gregory |
Re: [VFS] FTPS problem |
Fri, 07 Sep, 11:53 |
| Andreas Veithen (JIRA) |
[jira] [Resolved] (AXIOM-423) WSS4J fails when processing SAML Tokens since org.apache.axiom.om.impl.dom.NodeImpl has not implemented some required methods such as lookupNamespaceURI(), hence Rampart Trust module fails. |
Mon, 10 Sep, 08:30 |
| Andreas Veithen (JIRA) |
[jira] [Work started] (AXIOM-432) Updating the last child is not correct unless we are replacing the last child |
Mon, 10 Sep, 08:32 |
| Andreas Veithen (JIRA) |
[jira] [Assigned] (AXIOM-432) Updating the last child is not correct unless we are replacing the last child |
Mon, 10 Sep, 08:32 |
| Marc Giger (JIRA) |
[jira] [Created] (WSS-403) Use a common method for all of the P_hash implementations |
Mon, 10 Sep, 17:10 |
| Apache Wiki |
[Ws Wiki] Update of "FrontPage" by John Symbian |
Wed, 12 Sep, 02:44 |