[jira] [Updated] (RAMPART-362) Inter-operable issue with verifying signature and decrypting message with KeyInfo element when SAML token is used as protected token with WCF client

[ https://issues.apache.org/jira/browse/RAMPART-362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] asela pathberiya updated RAMPART-362: - Attachment: saml-wcf-rampart.patch saml-wcf-wss4j.patch Attaching possib

[jira] [Created] (RAMPART-362) Inter-operable issue with verifying signature and decrypting message with KeyInfo element when SAML token is used as protected token with WCF client

Inter-operable issue with verifying signature and decrypting message with KeyInfo element when SAML token is used as protected token with WCF client

[jira] [Updated] (RAMPART-361) Rampart can not accept Username token which is generated from WCF client. Due to name space qualified password type attribute in username token

[ https://issues.apache.org/jira/browse/RAMPART-361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] asela pathberiya updated RAMPART-361: - Attachment: RAMPART-361.patch I am attaching the patch for this issue. Thanks, Asela.

Re: issue when trying to reuse OperationClient?

My friend, i hope this helps you: /* * To change this template, choose Tools | Templates * and open the template in the editor. */ package org.kms.ws.client; import java.io.File; import java.io.FileOutputStream; import java.io.IOException; import java.net.URL; import java.util.ArrayList; impo

issue when trying to reuse OperationClient?

Hi I would like to reuse OperationClient across multiple (different) service invocations i.e. I plan to have at least one dedicated OperationClient per thread in a multi-threaded environment to avoid recreating it for each request and degrade performance since it is a big overhead. When I use

Re: Jenkins build is unstable: axis2-transports-trunk #731

On Thu, Apr 5, 2012 at 1:43 PM, Dimuthu Leelarathne wrote: > Hi all, > > Fixed the issue. Committed after running all tests in transports and > synapse. > Thanks. Synapse nightly build has stabilized. But I noticed that Axis2 transports nightly build is still failing: https://builds.apache.org/jo

Jenkins build is still unstable: axis2-transports-trunk #732

See - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org

[jira] [Commented] (AXIS2-5286) ConcurrentModificationException at AxisConfiguration

[ https://issues.apache.org/jira/browse/AXIS2-5286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13247269#comment-13247269 ] Hudson commented on AXIS2-5286: --- Integrated in Axis2 #1328 (See [https://builds.apache.org/j

Build failed in Jenkins: Axis2 #1327

See -- Failed to access build log hudson.util.IOException2: remote file operation failed: /home/jenkins/jenkins-slave/workspace/Axis2 at hudson.remoting.Channel@7b551ec3:ubuntu3 at hudson.FilePath.act(Fi

[jira] [Updated] (AXIS2-5287) Client stub creating empty node with values in request

[ https://issues.apache.org/jira/browse/AXIS2-5287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Mantri updated AXIS2-5287: - Description: 1) Generated client stub from WSDL using wsdl2java axis2. 2) Created requ

[jira] [Created] (AXIS2-5287) Client stub creating empty node with values in request

Client stub creating empty node with values in request -- Key: AXIS2-5287 URL: https://issues.apache.org/jira/browse/AXIS2-5287 Project: Axis2 Issue Type: Bug Components: adb, cli

Re: Jenkins build is unstable: axis2-transports-trunk #731

Hi all, Fixed the issue. Committed after running all tests in transports and synapse. thanks, dimuthu On Thu, Apr 5, 2012 at 12:46 PM, Dimuthu Leelarathne wrote: > Hi all, > > I am fixing this. > > thanks, > dimuthu > > > On Thu, Apr 5, 2012 at 2:12 AM, Andreas Veithen > wrote: > >> Probably c

Re: Jenkins build is unstable: axis2-transports-trunk #731

Hi all, I am fixing this. thanks, dimuthu On Thu, Apr 5, 2012 at 2:12 AM, Andreas Veithen wrote: > Probably caused by > http://svn.apache.org/viewvc?view=revision&revision=1308868 > > The usual problem with insufficient test coverage and commits without > unit tests... > > On Wed, Apr 4, 2012 a