Thanks Daniel. We are using CXF 2.3.2. Is it possible to do the same in this version? Thanks and regards, Anand R
From: Daniel Kulp <[email protected]> To: [email protected] Cc: Anand R <[email protected]> Date: 03-05-11 07:51 AM Subject: Re: Namespace Prefixes... On Monday, May 02, 2011 5:32:44 AM Anand R wrote: > Hello, > > Is it possible to control the namespace prefixes that gets generated in > the SOAP request? > > One of our Web service providers are only able to process SOAP request > that has a namespace prefix of soapenv for the SOAP Envelope. However, CXF > generates a prefix - soap. > > Even though this is not a standard requirement, is it possible to > customize this prefix? With CXF 2.4.0, you can fairly easily. You can configure in a property named: "soap.env.ns.map" which is just a map of prefix -> namespace for namespaces to write on the envelope. If one of them is the soap namespace, it will use that prefix. Dan > Thanks and regards, > Anand R > > > > > > DISCLAIMER: > > "The information in this e-mail and any attachment is intended only for > the person to whom it is addressed and may contain confidential and/or > privileged material. If you have received this e-mail in error, kindly > contact the sender and destroy all copies of the original communication. > IBS makes no warranty, express or implied, nor guarantees the accuracy, > adequacy or completeness of the information contained in this email or any > attachment and is not liable for any errors, defects, omissions, viruses > or for resultant loss or damage, if any, direct or indirect." -- Daniel Kulp [email protected] http://dankulp.com/blog Talend - http://www.talend.com DISCLAIMER: "The information in this e-mail and any attachment is intended only for the person to whom it is addressed and may contain confidential and/or privileged material. If you have received this e-mail in error, kindly contact the sender and destroy all copies of the original communication. IBS makes no warranty, express or implied, nor guarantees the accuracy, adequacy or completeness of the information contained in this email or any attachment and is not liable for any errors, defects, omissions, viruses or for resultant loss or damage, if any, direct or indirect."
