open a ticket CXF-6431.
2015-06-01 10:00 GMT+02:00 Aki Yoshida <[email protected]>: > Hi Stefan, > it looks like there is a bug in CXF. > Could you open an issue ticket in Jira? > thanks. > regards, aki > > 2015-05-29 13:22 GMT+02:00 Stefan Müller <[email protected]>: >> Hi, >> >> we are implementing an ebMS3 solution using cxf 3. The profile to be >> implemented has the following requirements: >> >> - SwA (no MTOM) >> - SOAP 1.2 >> - Due to the design of ebMS3 there is no WSDL >> >> As there is no WSDL we use the javax.xml.ws.Dispatch API with >> SOAPBinding.SOAP12HTTP_BINDING as binding. The message ebMS3 expects, >> according to its specification looks as follows: >> >> >> >> However, what we produce is as follows: >> >> >> >> The difference lies in the Content-Type of the root part, which is expected >> as application/soap+xml but set to text/xml. When testing against an Axis >> driven implementation we get the following error: >> >> >> Our dispatch method looks like this: >> >> >> >> Any help on how to get compatible with the Axis implementation is highly >> appreciated. >> >> Thanks >> Stefan >> >> >> >> >> >> >> -- >> View this message in context: >> http://cxf.547215.n5.nabble.com/SwA-Wrong-Content-Type-of-root-part-tp5757786.html >> Sent from the cxf-user mailing list archive at Nabble.com.
