Re: [Rampart] Can not run rampart-integration test

Hi Andreas, It seems r1442397 cause this issue after locally reverting r1442397 I can run tests successfully. Please take a look. Thanks ! On Fri, Mar 8, 2013 at 11:35 AM, Sagara Gunathunga wrote: > Hi devs, > > Getting following exception while running rampart-integration test any idea ? > > E

RE: Rampart and WSS4J 1.6.x - USERNAME_TOKEN validation in Rampart WS-Password Callback Handler

I did a little research and found that in the Rampart trunk, there is a change to address the issue below (also filed under https://issues.apache.org/jira/browse/RAMPART-374). The change is to introduce a custom RampartUsernameTokenValidator which is plugged in via the RampartMessageData. I am

Jenkins build is still unstable: sandesha2-trunk » Sandesha2 - Persistent Storage #1178

See - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]

Jenkins build became unstable: sandesha2-trunk » Sandesha2 - Test Suite #1178

See - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]

Jenkins build is still unstable: sandesha2-trunk #1178

See - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]

Re: AW: Cookie getting overwritten when client connects to multiple servers.

Hi Josef, Thanks for your time and reply. Yes I read about scope="soapsession", currently we are using scope="application". There are multiple reasons why we are using "application" and why we cannot change it to "soapsession" 1. Server initialization takes pretty long time as it has to collect

AW: Cookie getting overwritten when client connects to multiple servers.

Santhosh Did you ever read about scope="soapsession" ? this in contrast to ="application", ="transport" ="session". In scope="soapsession" the server issues a ServiceGroupId with the response to the initial request. The server has a init() and destroy() method in addition to business oriented m

[jira] [Updated] (AXIS2-5496) Code generation by axis2-wsdl2code-maven-plugin:1.6.2 fails in case wsdl with xsd:import schemaLocation and path to xsd contains a space character

[ https://issues.apache.org/jira/browse/AXIS2-5496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Demydenko updated AXIS2-5496: --- Attachment: log.txt > Code generation by axis2-wsdl2code-maven-plugin:1.6.2 fails in case

[jira] [Created] (AXIS2-5496) Code generation by axis2-wsdl2code-maven-plugin:1.6.2 fails in case wsdl with xsd:import schemaLocation and path to xsd contains a space character

Anton Demydenko created AXIS2-5496: -- Summary: Code generation by axis2-wsdl2code-maven-plugin:1.6.2 fails in case wsdl with xsd:import schemaLocation and path to xsd contains a space character Key: AXIS2-5496 UR