Return-Path: X-Original-To: apmail-axis-java-dev-archive@www.apache.org Delivered-To: apmail-axis-java-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D54CCC269 for ; Sat, 8 Jun 2013 19:26:20 +0000 (UTC) Received: (qmail 26363 invoked by uid 500); 8 Jun 2013 19:26:20 -0000 Delivered-To: apmail-axis-java-dev-archive@axis.apache.org Received: (qmail 26185 invoked by uid 500); 8 Jun 2013 19:26:20 -0000 Mailing-List: contact java-dev-help@axis.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: java-dev@axis.apache.org Delivered-To: mailing list java-dev@axis.apache.org Received: (qmail 26177 invoked by uid 99); 8 Jun 2013 19:26:20 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 08 Jun 2013 19:26:20 +0000 Date: Sat, 8 Jun 2013 19:26:20 +0000 (UTC) From: "Syed Ahmed Jeelani (JIRA)" To: java-dev@axis.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AXIS2-5581) The soap faults are being sent through InFlow pipe rather than InFaultFlow pipe. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AXIS2-5581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Syed Ahmed Jeelani updated AXIS2-5581: -------------------------------------- Description: We are using IBM Tivoli Directory Integrator v7.1.1 to create a solution to call Remote Webservices. IBM TDI Web service suite uses the apache axis2 to invoke the webservices. The requirement is such that, the web services is sending a response with a wsse:security header. I have developed a custom handler and used it in the InFlow PhaseOrder after the dispatch phase,(by creating a custom phase and adding the handler to it) of the axis2.xml file. But during the, if the web service return a soap-fault, then the instead of the InfaultFlow phaseOrder, inFlow phaseOrder is being used. was: We are using IBM Tivoli Directory Integrator v7.1.1 to create a solution to call Remote Webservices. The requirement is such that, the web services is sending a response with a wsse:security header. I have developed a custom handler and used it in the InFlow PhaseOrder after the dispatch phase,(by creating a custom phase and adding the handler to it) of the axis2.xml file. But during the, if the web service return a soap-fault, then the instead of the InfaultFlow phaseOrder, inFlow phaseOrder is being used. > The soap faults are being sent through InFlow pipe rather than InFaultFlow pipe. > -------------------------------------------------------------------------------- > > Key: AXIS2-5581 > URL: https://issues.apache.org/jira/browse/AXIS2-5581 > Project: Axis2 > Issue Type: Bug > Components: TCP transport > Affects Versions: 1.4 > Reporter: Syed Ahmed Jeelani > Labels: patch > Fix For: 1.4 > > Attachments: usingCustomConfigAxis2XML.log, usingDefaultAxis2Xml.log > > Original Estimate: 48h > Remaining Estimate: 48h > > We are using IBM Tivoli Directory Integrator v7.1.1 to create a solution to call Remote Webservices. IBM TDI Web service suite uses the apache axis2 to invoke the webservices. > The requirement is such that, the web services is sending a response with a wsse:security header. I have developed a custom handler and used it in the InFlow PhaseOrder after the dispatch phase,(by creating a custom phase and adding the handler to it) of the axis2.xml file. > But during the, if the web service return a soap-fault, then the instead of the InfaultFlow phaseOrder, inFlow phaseOrder is being used. > > > > class="org.apache.axis2.dispatchers.RequestURIBasedDispatcher"> > > > class="org.apache.axis2.dispatchers.SOAPActionBasedDispatcher"> > > > > > class="org.apache.axis2.dispatchers.AddressingBasedDispatcher"> > > > > > > > class="org.apache.axis2.dispatchers.RequestURIBasedDispatcher"/> > class="org.apache.axis2.dispatchers.SOAPActionBasedDispatcher"/> > class="org.apache.axis2.dispatchers.RequestURIOperationDispatcher"/> > class="org.apache.axis2.dispatchers.SOAPMessageBodyBasedDispatcher"/> > class="org.apache.axis2.dispatchers.HTTPLocationBasedDispatcher"/> > class="org.apache.axis2.jaxws.dispatchers.GenericProviderDispatcher"/> > class="org.apache.axis2.jaxws.dispatchers.MustUnderstandValidationDispatcher"/> > > > > > class="com.test.service.phase.handler.SecurityHeaderHandler"/> > > > > class="org.apache.axis2.jaxws.dispatchers.MustUnderstandChecker"> > > > > > > > > > > > > > > > > > > > class="org.apache.axis2.dispatchers.AddressingBasedDispatcher"> > > > > > > > class="org.apache.axis2.dispatchers.RequestURIBasedDispatcher"/> > class="org.apache.axis2.dispatchers.SOAPActionBasedDispatcher"/> > class="org.apache.axis2.dispatchers.RequestURIOperationDispatcher"/> > class="org.apache.axis2.dispatchers.SOAPMessageBodyBasedDispatcher"/> > class="org.apache.axis2.dispatchers.HTTPLocationBasedDispatcher"/> > class="org.apache.axis2.jaxws.dispatchers.GenericProviderDispatcher"/> > class="org.apache.axis2.jaxws.dispatchers.MustUnderstandValidationDispatcher"/> > > > > > > > > > > > > > > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org For additional commands, e-mail: java-dev-help@axis.apache.org