Mailing-List: contact users-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cxf.apache.org
Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <25227953.post@talk.nabble.com>
Date: Mon, 31 Aug 2009 11:14:33 -0700 (PDT)
From: superk888 <superk888@gmail.com>
To: users@cxf.apache.org
Subject: Re: Invoking a CXF web service with a SIMPLE FRONTEND !!!
In-Reply-To: <200908311055.46490.dkulp@apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
References: <25215876.post@talk.nabble.com>
 <61b5d9410908301746m2d9f69cag71ec9221ac7f5a72@mail.gmail.com>
 <25218968.post@talk.nabble.com> <25219284.post@talk.nabble.com>
 <25220781.post@talk.nabble.com>
 <61b5d9410908310416t4e2faec0kaa411570530c18@mail.gmail.com>
 <25222320.post@talk.nabble.com> <200908311055.46490.dkulp@apache.org>


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 th=
e
default MTOM status of Apache CXF is off).

But I'll have to test my application thoroughly tomorrow (wouldn't been abl=
e
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 t=
o
help me solve my issue.
Really, I appreciate :handshake:


dkulp wrote:
>=20
> =20
> Can you capture the incoming request from Axis2?   I THINK the
> Content-Type=20
> head is probably different.   It probably contains a charset in it
> someplace=20
> (or it's not mime).     Basically, per spec, if there isn't a charset
> there,=20
> the default is ISO8859-1.    It LOOKS like when it's mime, we may not be=
=20
> resetting it to the charset defined in the mime boundary, which is
> probably a=20
> bug.  =20
>=20
> In anycase, I'd like to see the Axis2 and/or SOAPUI messages to see if
> they=20
> are different.  =20
>=20
> One possible way to "fix" it would be to turn off MTOM on the client side=
.    =20
> That may fix it as well as the message would be sent out non-mime encoded
> and=20
> the charset should be on the Content-Type header.
>=20
>=20
> Dan
>=20
>=20
>=20
>=20
> 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 o=
f
>> 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<superk888@gmail.com> wrote:
>> >> While  still working on this issue by doing a lot of (silly) tests, i=
t
>> >> 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 "=C3=A9" and "=C3=A8" into notepad++ an=
d changing
>> >> the format to ANSI --> "=C3=83=C2=A9" and "=C3=83=C2=A8")
>> >>
>> >> 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=3D"application/xop+xml";
>> >>> boundary=3D"uuid:f5cde3e3-b98e-4483-9562-55892bc754bf";
>> >>> start=3D"<root.message@cxf.apache.org>"; start-info=3D"text/xml"
>> >>> Headers: {Content-Length=3D[693], Date=3D[Mon, 31 Aug 2009 07:13:49 =
GMT],
>> >>> Server=3D[Apache-Coyote/1.1], content-type=3D[multipart/related;
>> >>> type=3D"application/xop+xml";
>> >>> boundary=3D"uuid:f5cde3e3-b98e-4483-9562-55892bc754bf";
>> >>> start=3D"<root.message@cxf.apache.org>"; start-info=3D"text/xml"]}
>> >>> Payload:
>> >>> --uuid:f5cde3e3-b98e-4483-9562-55892bc754bf
>> >>> Content-Type: application/xop+xml; charset=3DUTF-8; type=3D"text/xml=
";
>> >>> Content-Transfer-Encoding: binary
>> >>> Content-ID: <root.message@cxf.apache.org>
>> >>>
>> >>> <soap:Envelope
>> >>>
>> xmlns:soap=3D"http://schemas.xmlsoap.org/soap/envelope/"><soap:Body><ns2=
:
>> >>>sendRequestResponse
>> >>>
>> xmlns:ns2=3D"http://wsController.webServices.web.forhrm.formatech.be/"><=
n
>> >>>s2:response>&lt;?xml version=3D&quot;1.0&quot;
>> >>>
>> encoding=3D&quot;ISO-8859-1&quot;?&gt;&lt;Response&gt;&lt;ReturnCode&gt;=
0
>> >>>00&lt;/ReturnCode&gt;&lt;ReturnMessage&gt;Syst=C3=A8me&lt;/ReturnMess=
age&gt;&
>> >>>lt;/Response&gt;</ns2:response></ns2:sendRequestResponse></soap:Body>=
</s
>> >>>oap:Envelope> --uuid:f5cde3e3-b98e-4483-9562-55892bc754bf--
>> >>> --------------------------------------
>> >>>
>> >>> RESPONSE (translate - SYSTEM):
>> >>>  <?xml version=3D"1.0"
>> >>>
>> encoding=3D"ISO-8859-1"?><Response><ReturnCode>000</ReturnCode><ReturnMe=
s
>> >>>sage>Syst=C3=83=C2=A8me</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<superk888@gmail.com>
>> 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 "=C3=A9", my CXF fronte=
nd
>> >>>>>> returns
>> >>>>>> "=C3=83=C2=A8".
>> >>>>>> 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 m=
e
>> >>>>>> 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 face=
d
>> >>>>>> 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.
>=20
> --=20
> Daniel Kulp
> dkulp@apache.org
> http://www.dankulp.com/blog
>=20
>=20

--=20
View this message in context: http://www.nabble.com/Invoking-a-CXF-web-serv=
ice-with-a-SIMPLE-FRONTEND-%21%21%21-tp25215876p25227953.html
Sent from the cxf-user mailing list archive at Nabble.com.