[jira] [Created] (AXIS2-5391) AxisService2WSDL20 fails to return the WSDL 2.0 styles when the schema has a ComplexElement with XmlSchemaAny

lakmali erandi baminiwatta created AXIS2-5391: - Summary: AxisService2WSDL20 fails to return the WSDL 2.0 styles when the schema has a ComplexElement with XmlSchemaAny Key: AXIS2-5391 URL: https://issue

[AXIS2]Transport setting http response satus not working

Hello, I'd like the ability to to change the response status based on our functional requirement for implementing CMIS 1.0 specification For example : I'd like to send in certain cases an http 503 (instead of a 500) when a soap fault occurs. HttpServletResponse resp = (HttpServletRespon

[jira] [Updated] (AXIS2-5391) AxisService2WSDL20 fails to return the WSDL 2.0 styles when the schema has a ComplexElement with XmlSchemaAny

[ https://issues.apache.org/jira/browse/AXIS2-5391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lakmali erandi baminiwatta updated AXIS2-5391: -- Attachment: AXIS2-5391.diff Attached the patch (created for axis2-trunk

RE: [jira] [Created] (AXIS2-5391) AxisService2WSDL20 fails to return the WSDL 2.0 styles when the schema has a ComplexElement with XmlSchemaAny

package org.apache.axis2.description public class AxisService2WSDL20 implements WSDL2Constants . private URI [] checkStyle(AxisOperation axisOperation) throws URISyntaxException, AxisFault { Object next = iterator.next();

[jira] [Commented] (RAMPART-261) Ability to Toggle "mustUnderstand" flag in security header.

[ https://issues.apache.org/jira/browse/RAMPART-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13436079#comment-13436079 ] Enda Diggins commented on RAMPART-261: -- I also had this problem; resolved by patchin

[jira] [Updated] (AXIS2-5379) The third URL parameter can not be processed (REST web service with WSDL 2.0)

[ https://issues.apache.org/jira/browse/AXIS2-5379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sven Strohschein updated AXIS2-5379: Priority: Blocker (was: Critical) > The third URL parameter can not be processed (REST

Fwd: Mandatory svnpubsub migration by Jan 2013

FYI: As required by the mail below, I've requested migration to svnpubsub for the Axis sites; see INFRA-5152. In practice, there are only two things that change for release managers: 1. The locations of the generated sites in SVN have changed: they are now all under https://svn.apache.org/repos/as

Build failed in Jenkins: axis2-transports-trunk #982

See Changes: [veithen] Removed unnecessary repositories. -- [...truncated 428 lines...] Aug 16, 2012 9:09:48 PM org.apache.axis2.transport.base.AbstractTransportSender init INFO: TCP Sende

Jenkins build is back to normal : axis2-transports-trunk #983

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