Return-Path: Delivered-To: apmail-cxf-issues-archive@www.apache.org Received: (qmail 72132 invoked from network); 10 Jul 2009 06:42:28 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 10 Jul 2009 06:42:28 -0000 Received: (qmail 27552 invoked by uid 500); 10 Jul 2009 06:42:38 -0000 Delivered-To: apmail-cxf-issues-archive@cxf.apache.org Received: (qmail 27440 invoked by uid 500); 10 Jul 2009 06:42:37 -0000 Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cxf.apache.org Delivered-To: mailing list issues@cxf.apache.org Received: (qmail 27419 invoked by uid 99); 10 Jul 2009 06:42:37 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Jul 2009 06:42:36 +0000 X-ASF-Spam-Status: No, hits=-1997.8 required=10.0 tests=ALL_TRUSTED,DEAR_SOMETHING X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Jul 2009 06:42:35 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id C95E9234C004 for ; Thu, 9 Jul 2009 23:42:14 -0700 (PDT) Message-ID: <1882959125.1247208134810.JavaMail.jira@brutus> Date: Thu, 9 Jul 2009 23:42:14 -0700 (PDT) From: "Mihir Shelat (JIRA)" To: issues@cxf.apache.org Subject: [jira] Created: (CXF-2336) SOAP Binding (i.e. SOAP Version) of out going message should be same as incoming message MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org SOAP Binding (i.e. SOAP Version) of out going message should be same as incoming message ---------------------------------------------------------------------------------------- Key: CXF-2336 URL: https://issues.apache.org/jira/browse/CXF-2336 Project: CXF Issue Type: Improvement Components: Soap Binding Reporter: Mihir Shelat Dear Sir, Currently I am evaluating various Webservice Frameworks such as Axis2, CXF and Spring WS. In CXF the default SOAP Binding (i.e. SOAPVersion) is SOAP 1.1. So if you don't set any binding in your webservice, by default the SOAP version of outgoing message is 1.1. CXF allows configuring the SOAP binding of outgoing message either using Annotations OR Spring Configuration. No matter whatever is the SOAP Binding of incoming message, CXF always uses the binding specified at server side for out going message. Like wise AXIS2, for outgoing messages, CXF should use the same SOAP Binding as that of incoming message instead of the one configured in the server. This allows webservices to be more interoperable and SOAP Binding agnostic. Let me know if there is any way by which I can configure CXF to use the same SOAP Binding as that of incoming message. If it is not possible, can we incorporate this improvement in the next release? One of the criteria for webservice framework selection is simultaneous support of SOAP 1.1 and SOAP1.2 bindings. Thanks, Mihir -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.