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/";><ns2:response><?xml version="1.0" encoding="ISO-8859-1"?><Response><ReturnCode>000</ReturnCode><ReturnMessage>Système</ReturnMessage></Response></ns2:response></ns2:sendRequestResponse></soap:Body></soap:Envelope> --uuid:f5cde3e3-b98e-4483-9562-55892bc754bf-- -------------------------------------- RESPONSE (translate - SYSTEM): <?xml version="1.0" encoding="ISO-8859-1"?><Response><ReturnCode>000</ReturnCode><ReturnMessage>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-FRONTEND-%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-tp25215876p25219284.html Sent from the cxf-user mailing list archive at Nabble.com.
