Turns out my problem had to do with MTOM indeed. It seems to be fixed by switching MTOM ON on the client side (after having read your suggestion, I googled a while and I've read - but too bad, can't remember where - that the default MTOM status of Apache CXF is off).
But I'll have to test my application thoroughly tomorrow (wouldn't been able to spend one more hour at work after a 10+ hours Monday, especially after almost 2 whole weeks of frustration on the same issue) Anyway, I really wanted to thank all of you guys, who spared me some time to help me solve my issue. Really, I appreciate :handshake: dkulp wrote: > > > Can you capture the incoming request from Axis2? I THINK the > Content-Type > head is probably different. It probably contains a charset in it > someplace > (or it's not mime). Basically, per spec, if there isn't a charset > there, > the default is ISO8859-1. It LOOKS like when it's mime, we may not be > resetting it to the charset defined in the mime boundary, which is > probably a > bug. > > In anycase, I'd like to see the Axis2 and/or SOAPUI messages to see if > they > are different. > > One possible way to "fix" it would be to turn off MTOM on the client side. > > That may fix it as well as the message would be sent out non-mime encoded > and > the charset should be on the Content-Type header. > > > Dan > > > > > On Mon August 31 2009 7:58:11 am superk888 wrote: >> Having ISO8859-1 is OK: more precisely, the service I've developed is an >> existing application that I've exposed as a web service with CXF. The >> existing application consists in an application that is deployed on >> Tomcat >> and gets HttpRequest... >> >> With my web service deployed, the client sends the XML content instead of >> a >> whole HTTP request. >> Consequently, the XML request has been built "manually". >> >> Besides, an AXIS2 client doesn't face the described issue. So I really >> don't think it has anything to do with Tomcat ... >> >> bimargulies wrote: >> > ISO8859-1 is NOT UTF-8. You need to find out why you have ISO-8859-1 >> > in that header. I suspect Tomcat. >> > >> > On Mon, Aug 31, 2009 at 5:45 AM, superk888<[email protected]> wrote: >> >> While still working on this issue by doing a lot of (silly) tests, it >> >> has >> >> come to my attention that my CXF simple frontend seems to sort of >> >> convert the SOAP response which is encoded in ISO-8859-1/UTF-8 into >> >> ANSI. >> >> >> >> (I've realized that by typing "é" and "è" into notepad++ and changing >> >> the format to ANSI --> "é" and "è") >> >> >> >> Could this be a clue? >> >> >> >> superk888 wrote: >> >>> If that could help anyway, here is the inbound soap message content, >> >>> with >> >>> the corresponding String type response my CXF Frontend gives me (in >> >>> bold; >> >>> the character encoding problem I was talking about): >> >>> >> >>> INFO: Inbound Message >> >>> ---------------------------- >> >>> ID: 2 >> >>> Encoding: ISO-8859-1 >> >>> Content-Type: multipart/related; type="application/xop+xml"; >> >>> boundary="uuid:f5cde3e3-b98e-4483-9562-55892bc754bf"; >> >>> start="<[email protected]>"; start-info="text/xml" >> >>> Headers: {Content-Length=[693], Date=[Mon, 31 Aug 2009 07:13:49 GMT], >> >>> Server=[Apache-Coyote/1.1], content-type=[multipart/related; >> >>> type="application/xop+xml"; >> >>> boundary="uuid:f5cde3e3-b98e-4483-9562-55892bc754bf"; >> >>> start="<[email protected]>"; start-info="text/xml"]} >> >>> Payload: >> >>> --uuid:f5cde3e3-b98e-4483-9562-55892bc754bf >> >>> Content-Type: application/xop+xml; charset=UTF-8; type="text/xml"; >> >>> Content-Transfer-Encoding: binary >> >>> Content-ID: <[email protected]> >> >>> >> >>> <soap:Envelope >> >>> >> xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";><soap:Body><ns2: >> >>>sendRequestResponse >> >>> >> xmlns:ns2="http://wsController.webServices.web.forhrm.formatech.be/";><n >> >>>s2:response><?xml version="1.0" >> >>> >> encoding="ISO-8859-1"?><Response><ReturnCode>0 >> >>>00</ReturnCode><ReturnMessage>Système</ReturnMessage>& >> >>>lt;/Response></ns2:response></ns2:sendRequestResponse></soap:Body></s >> >>>oap:Envelope> --uuid:f5cde3e3-b98e-4483-9562-55892bc754bf-- >> >>> -------------------------------------- >> >>> >> >>> RESPONSE (translate - SYSTEM): >> >>> <?xml version="1.0" >> >>> >> encoding="ISO-8859-1"?><Response><ReturnCode>000</ReturnCode><ReturnMes >> >>>sage>Système</ReturnMessage></Response> >> >>> >> >>> superk888 wrote: >> >>>> Is it possible to configure programmatically characters encoding >> >>>> parameters of the simple frontend? >> >>>> >> >>>> bimargulies wrote: >> >>>>> This feels like a Unicode problem. How is your service deployed? >> (and >> >>>>> with what version of CXF)? >> >>>>> >> >>>>> On Sun, Aug 30, 2009 at 5:24 PM, superk888<[email protected]> >> wrote: >> >>>>>> Hi everybody, >> >>>>>> >> >>>>>> I have developed and deployed successfully a simple web service >> with >> >>>>>> CXF. >> >>>>>> The service is really simple : it gets a String parameter and >> return >> >>>>>> a >> >>>>>> String response. I've tried to invoke this service with an AXIS2 >> >>>>>> client >> >>>>>> and >> >>>>>> all went as expected. But when I try to invoke the same service >> with >> >>>>>> a >> >>>>>> CXF >> >>>>>> simple Frontend, the accented characters are not interpreted >> >>>>>> correctly. >> >>>>>> For >> >>>>>> instance, when the SOAP response contains "é", my CXF frontend >> >>>>>> returns >> >>>>>> "è". >> >>>>>> I've added LoggingInterceptors to check the SOAP >> requests/responses >> >>>>>> content >> >>>>>> and they turn out to be correct. >> >>>>>> >> >>>>>> Has anybody already faced the same problem? Could somebody help me >> >>>>>> to solve >> >>>>>> it? >> >>>>>> >> >>>>>> PS : I've decided to use a simple frontend because my service >> >>>>>> consumer >> >>>>>> has >> >>>>>> to be integrated in a RCP project and after many attempts, I faced >> >>>>>> other >> >>>>>> problems using the JAX-WS and the dynamic clients. >> >>>>>> -- >> >>>>>> View this message in context: >> >>>>>> >> http://www.nabble.com/Invoking-a-CXF-web-service-with-a-SIMPLE-FRONT >> >>>>>>END-%21%21%21-tp25215876p25215876.html Sent from the cxf-user >> mailing >> >>>>>> list archive at Nabble.com. >> >> >> >> -- >> >> View this message in context: >> >> >> http://www.nabble.com/Invoking-a-CXF-web-service-with-a-SIMPLE-FRONTEND- >> >>%21%21%21-tp25215876p25220781.html Sent from the cxf-user mailing list >> >> archive at Nabble.com. > > -- > Daniel Kulp > [email protected] > http://www.dankulp.com/blog > > -- View this message in context: http://www.nabble.com/Invoking-a-CXF-web-service-with-a-SIMPLE-FRONTEND-%21%21%21-tp25215876p25227953.html Sent from the cxf-user mailing list archive at Nabble.com.
