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 50471E261 for ; Sun, 3 Feb 2013 15:18:15 +0000 (UTC) Received: (qmail 88848 invoked by uid 500); 3 Feb 2013 15:18:14 -0000 Delivered-To: apmail-axis-java-dev-archive@axis.apache.org Received: (qmail 88639 invoked by uid 500); 3 Feb 2013 15:18:14 -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 88610 invoked by uid 99); 3 Feb 2013 15:18:14 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 03 Feb 2013 15:18:14 +0000 Date: Sun, 3 Feb 2013 15:18:14 +0000 (UTC) From: "Sagara Gunathunga (JIRA)" To: java-dev@axis.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AXIS2-5480) SOAPAction being set even when WSDL has soapAction="" 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-5480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13569797#comment-13569797 ] Sagara Gunathunga commented on AXIS2-5480: ------------------------------------------- Last comment is due to a mistake I did, I used wrong issue id when applying patch to a different issue. Please ignore last comment generated by Jenkins. > SOAPAction being set even when WSDL has soapAction="" > ----------------------------------------------------- > > Key: AXIS2-5480 > URL: https://issues.apache.org/jira/browse/AXIS2-5480 > Project: Axis2 > Issue Type: Bug > Components: wsdl > Affects Versions: 1.6.2 > Reporter: Wayne Holmes > Attachments: IMSWebService.wsdl > > > Upgraded our Web Service to use CXF 1.5.5 and our existing AXIS2 clients fail out with message > - The given SOAPAction http://text2idml.idml.server.cequint.com/Text2IDMLWebServiceImpl/queryHandsets does not match an operation. > Based on the comments in the security fix in CXF 1.5.5, it appears CXF is expecting the SOAPAction to be "" since that is what is in the CXF generated WSDL. (See http://cxf.apache.org/cve-2012-3451.html) > We did a trace with CXF, SoapUI and .Net clients, and those clients all specify a SOAPAction="" in the headers. > Deepal Jayasinghe ended up suggesting that I write this bug and attach a copy of our WSDL. Complete history of various workaround attempted may be found in the AXIS mailing list with subject "SOAPAction value in AXIS generated stubs causing problems with server upgrade to CXF 1.5.5 from CXF 1.5.0". -- 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