Return-Path: X-Original-To: apmail-cxf-dev-archive@www.apache.org Delivered-To: apmail-cxf-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 25C50EFA6 for ; Thu, 7 Feb 2013 15:02:26 +0000 (UTC) Received: (qmail 25256 invoked by uid 500); 7 Feb 2013 15:02:25 -0000 Delivered-To: apmail-cxf-dev-archive@cxf.apache.org Received: (qmail 24670 invoked by uid 500); 7 Feb 2013 15:02:21 -0000 Mailing-List: contact dev-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 dev@cxf.apache.org Delivered-To: moderator for dev@cxf.apache.org Received: (qmail 13021 invoked by uid 99); 7 Feb 2013 14:58:36 -0000 X-ASF-Spam-Status: No, hits=-0.1 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of prvs=743de7d5e=tripatjeet.singh@tcs.com designates 219.64.33.222 as permitted sender) X-IronPort-AV: E=Sophos;i="4.84,622,1355077800"; d="scan'208,217";a="120989177" From: "Tripatjeet Singh" To: "dev@cxf.apache.org" Subject: Issues after upgrading from CXF 2.2.9 to CXF 2.6.2 Thread-Topic: Issues after upgrading from CXF 2.2.9 to CXF 2.6.2 Thread-Index: AQHOBUOJo6a9udv/S0qJsct2wPUB4Q== Date: Thu, 7 Feb 2013 14:58:06 +0000 Message-ID: <54430D464C1B0841BBC364F54FC0146313FCB309@INMUMEXM01> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.19.142.10] MIME-Version: 1.0 X-MIMETrack: Itemize by SMTP Server on InMumH01/TCS(Release 8.5.2FP4|November 17, 2011) at 02/07/2013 20:28:08, Serialize by Router on InMumH01/TCS(Release 8.5.2FP4|November 17, 2011) at 02/07/2013 20:28:08, Serialize complete at 02/07/2013 20:28:08 X-TNEFEvaluated: 1 Content-Type: multipart/alternative; boundary="_000_54430D464C1B0841BBC364F54FC0146313FCB309INMUMEXM01_" Content-Language: en-US X-Virus-Checked: Checked by ClamAV on apache.org --_000_54430D464C1B0841BBC364F54FC0146313FCB309INMUMEXM01_ Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Hi Team, I am facing issues after upgrading the CXF version from 2.2.9 to 2.6.2 . Th= e web service is created and deployed using AXIS1.3 and the consumer/client= is using cxf. But after upgrading the cxf version from 2.2.9 to 2.6.2 we c= an see a difference in the security part of the header. There are some name= spaces found missing due to which the response is failing with Signature Ve= rification Error as the FaultString. Can you please help me with this issue. Its kind of very critical at the mo= ment. Is cxf 2.6.2 comaptible with AXIS 1.3 ? Can we do any workarounds to = make it work ?Will surely appreciate your response. Thanks and Regards, Tripatjeet Singh Cell : +91 9739 008 674 Mail to : tripatjeet.singh@tcs.com =3D=3D=3D=3D=3D-----=3D=3D=3D=3D=3D-----=3D=3D=3D=3D=3D Notice: The information contained in this e-mail message and/or attachments to it may contain = confidential or privileged information. If you are = not the intended recipient, any dissemination, use, = review, distribution, printing or copying of the = information contained in this e-mail message = and/or attachments to it are strictly prohibited. If = you have received this communication in error, = please notify us by reply e-mail or telephone and = immediately and permanently delete the message = and any attachments. Thank you --_000_54430D464C1B0841BBC364F54FC0146313FCB309INMUMEXM01_--