Re: axis2 1.8/rampart 1.8

I've been involved long enough in Open Source projects to know that making promises about the ETA of a new major release is generally not a good idea. If you need fixes for specific issues, it might actually be better to merge them to the 1.7.x maintenance branch, because that branch is kept in a s

[jira] (RAMPART-391) Add ability to set the wsiBspCompliant property in WSSConfig

[ https://issues.apache.org/jira/browse/RAMPART-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen updated RAMPART-391: Labels: (was: bsp-compliance property) > Add ability to set the wsiBspCompliant property

[jira] (RAMPART-390) SupportingToken assertions do not support multiple nested protection assertions

[ https://issues.apache.org/jira/browse/RAMPART-390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen updated RAMPART-390: Labels: Patch (was: ) > SupportingToken assertions do not support multiple nested protecti

[jira] (RAMPART-390) SupportingToken assertions do not support multiple nested protection assertions

[ https://issues.apache.org/jira/browse/RAMPART-390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen updated RAMPART-390: Description: The SupportingToken class in the rampart-policy component will only handle one

[jira] (RAMPART-389) RampartException: "Unexpected signature" thrown on client side when the service policy requires SignatureConfirmation and it is the only signed element.

[ https://issues.apache.org/jira/browse/RAMPART-389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen updated RAMPART-389: Labels: Patch (was: ) > RampartException: "Unexpected signature" thrown on client side whe

axis2 1.8/rampart 1.8

Hi Andreas, Do you have any timeline for 1.8 release for both axis2 and rampart? I see a flurry of activity related to JIRA issues. Any ETA for the new releases? George