Hi, What exactly the problem you have with unwanted namespace declaration? Can your server parse the envelope? Normally low level XML libraries like Xerces cannot guarantee that things like #1 don't happen by XML serialization.
Regards, Andrei. > -----Original Message----- > From: Deepak Kumar [mailto:[email protected]] > Sent: Dienstag, 20. Januar 2015 12:28 > To: [email protected] > Subject: Re: CXF library add the unwanted namespace in SOAP outgoing request > > My problem is #1, and in our case we get the entire SoapEnvelope (XMl) with > namespaces added from Client, so we do not have any control over it to parse > and add custom namespace. IS there any way the SOAPMessage object we > supplied should not be modified or how to provide the original SoapMessage > before invoking the SOAP (over the wire)? > > Thanks, > Deepak > > On Tue, Jan 20, 2015 at 4:18 PM, Aki Yoshida <[email protected]> wrote: > > > what is exactly the symptom? > > 1. an unwanted namespace declaration is added? > > 2. a different prefix is used for some namespace? > > 3. a different namespace is used? > > > > I think 1 and 2 are possible but 3 should not happen. > > If your problem is 2, you can control this behavior by passing your > > custom namespace prefix map using the property key soap.env.ns.map in > > the request context. > > > > > > 2015-01-20 11:02 GMT+01:00 Deepak Kumar <[email protected]>: > > > Hi, > > > > > > In my implementation, the javax.xml.soap.SOAPMessage object is > > > created > > and > > > CXF libraries are used for JAX WS implementation and > > > org.apache.cxf.jaxws.DispatchImpl object is created for dispatch, > > > but I > > saw > > > the original soapmessage is created with envelope is different than > > actual > > > message transmitted, I saw in wireshark trace, the transmitted soap > > > envelope has extra namespaces added by CXF library. Is there any way > > > to disable auto added namespaces by CXF libraries. > > > > > > > > > --Deepak > >
