Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-user@ws.apache.org
Received-SPF: pass (asf.osuosl.org: domain of davanum@gmail.com designates
 64.233.162.205 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=narqi/QQvSoCLR1A3A6SkMpqTGeihe2xIIZU9XnJ2K1qGkdSWfOOIeP4BpyJCJ1lh2VyzZt3evu4WphaL0kIFE4wn1B5R8G3UCJcYhUfDi/hF4JAnC8evoVA2q6Sb67qoC8hQz/GUrLP78rF8JaGwKoimZES1Ye37JdUMQJ7iIw=
Message-ID: <19e0530f0605180432p51f81e0bj69c52a6505b83e5d@mail.gmail.com>
Date: Thu, 18 May 2006 07:32:29 -0400
From: "Davanum Srinivas" <davanum@gmail.com>
Reply-To: dims@apache.org
To: axis-user@ws.apache.org
Subject: Re: [AXIS2] Encoding problems
In-Reply-To: <003201c67a51$95e43b20$5410a8c0@Laurent>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <003201c67a51$95e43b20$5410a8c0@Laurent>

Laurent,

Could u please create a JIRA issue
(http://issues.apache.org/jira/browse/AXIS2) and upload your code,
wsdl what ever you think we need to recreate the problem.

thanks,
dims

On 5/18/06, Laurent CELLA <laurent.cella@inexbee.com> wrote:
>
>
> Hi dear Axis users and contributors.
>
> We have several problem with encoding issues in Axis 2.
>
> We are working on a project with webservices : Axis 2 ( rel 0.95 ) with
> Apache Tomcat 5.5 as a container.
> The project involves SOAP with attachment requests, and for now we dont u=
se
> any AXIS-Generated client but a custom client based on Apache commons
> HttpClient and javax.mail.internet packages to post a SOAP with attachmen=
t
> request over Http.
> We have choosen RPC-Literal encoding.
>
> We have been successfull in making our service work ( integrated in Tomca=
t
> 5) in most generic uses cases, but we have problems with encoding issues.
>
> ***
> Typically our request contains XML data beared by the SOAP Body with
> references to attachments content-ids in it.
>
> The problem occurs when this XML contains special characters ( like
> iso-latin accents ) or when one attachment has a content-transfer-encodin=
g
> "quoted-printable".
>
> To handle special characters in the main XML we have tried those solution=
s :
>
> 1. Put the special characters "as they are", specifying "utf-8" encoding =
and
> waiting implicitly for them at server side.
>
> 2. content-transfer-encoding =3D "quoted-printable" ( as it should be the=
 case
> with some of the text attachments )
>
> 3. explicitly encodes with RFC 2048 some of the xml fields ( assuming tha=
t
> Server should know wich fields to decode with MimeUtility.decodeText(
> ... ) )
>
>
> Before going any further, the goal of our email is to understand what rel=
ies
> on our misunderstanding of AXIS API, and what relies on known bugs or "no=
t
> yet implemented features".
>
> ***
>
> Solution 1 :
> Whatever we tryied, the JVM encoding ( "file.encoding" property ) seems t=
o
> cause problems.
>
> Solution 3 :
> The MimeUtility.decodeWord( ... ) or MimeUtility.decodeText( ... ) that a=
re
> located in geronimo-spec-javamail-1.3.1-rc5.jar
> does absolutely nothing and does not threw any exceptions. When replaced
> with mail-1.3.1.jar it works.
> So it seems the jar is bugged or not completed.
> It is the same with release 1.0 ( it provides the same jar )
> I cant replace the jar to solve the problem, cause geronimo contains and
> maps to content-handlers to handles attachments at server side.
>
> Solution 2 :
> With a HTTP Request like this ( tcpmon capture ) I get an exception ( tha=
t
> follows the capture ),
> that makes us think that this feature is not yet implemented  ( or that o=
ur
> invocation is wrong ).
>
> POST /DocAccess_v0.1_Feeder/services/DocAccessService
> HTTP/1.1
> Content-type: multipart/related;
>        boundary=3D"----=3D_Part_1_20639876.1146648323575";
>        start=3D"</doc-access-soap/process-request>";
> type=3D"application/xop+xml; charset=3Dutf-8"
> User-Agent: Jakarta Commons-HttpClient/3.0-rc4
> Host: localhost:8081
> Content-Length: 962
>
> ------=3D_Part_1_20639876.1146648323575
> Content-Type: application/xop+xml; charset=3Dutf-8
> Content-Transfer-Encoding: quoted-printable
> Content-ID: </doc-access-soap/process-request>
>
> <?xml version=3D3D"1.0" encoding=3D3D"utf-8"?>
> <soapenv:Envelope
> xmlns:soapenv=3D3D"http://schemas.xmlsoap.org/soap/envelope=3D
> /">
> <soapenv:Body
> xmlns:types=3D3D"http://www.inexbee.com/m2doc/m2doc">
> <processRequest
> xmlns=3D3D"http://www.inexbee.com/m2doc/m2doc"
>     vasId=3D3D"m2gateway-test" vasPassword=3D3D"inexbee" mailProcessReque=
st=3D3D"=3D
> true">
>     <user authMethod=3D3D"msisdn" authString=3D3D"+33611223344"/>
>     <mail sender=3D3D"mail.from@inexbee.com"
> timestampMillis=3D3D"1146648323575=3D
> ">
>         <subject>RE : MET demo by Inexbee: =3DC3=3DA0=3DC3=3DA9=3DC3=3DB9=
=3DC3=3DB1=3DE2=3D82=3D
> =3DAC.</subject>
>         <body>Respuesta desde Outlook XP : =3DC3=3DA0=3DC3=3DA9=3DC3=3DB9=
=3DC3=3DB1=3DE2=3D82=3D
> =3DAC</body>
>     </mail>
> </processRequest>
> </soapenv:Body></soapenv:Envelope>
>
> ------=3D_Part_1_20639876.1146648323575--
>
> The result is ( it is an HTML tomcat trace )
>
> <?xml version=3D'1.0' encoding=3D'UTF-8'?><soapenv:Envelope
> xmlns:soapenv=3D"http://www.w3.org/2003/05/soap-envelope"><soapenv:Header
> /><soapenv:Body><soapenv:Fault><soapenv:Code><soapenv:Value>soapenv:Sende=
r</soapenv:Value></soapenv:Code><soapenv:Reason><soapenv:Text
> xml:lang=3D"en-US">Unexpected character '3' (code 51); expected a quote
> character enclosing value for 'version'
>  at [row,col {unknown-source}]: [1,15]; nested exception is:
>        com.ctc.wstx.exc.WstxUnexpectedCharException:
> Unexpected character
> '3' (code 51); expected a quote character enclosing value for 'version'
>  at [row,col {unknown-source}]:
> [1,15]</soapenv:Text></soapenv:Reason><soapenv:Detail><Exception
> xmlns=3D"">org.apache.axis2.AxisFault: Unexpected character '3' (code 51)=
;
> expected a quote character enclosing value for 'version'
>  at [row,col {unknown-source}]: [1,15]; nested exception is:
>        com.ctc.wstx.exc.WstxUnexpectedCharException:
> Unexpected character
> '3' (code 51); expected a quote character enclosing value for 'version'
>  at [row,col {unknown-source}]: [1,15]
>        at
> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest=
(HTTPTransportUtils.java:297)
>        at
> org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:160)
>        at
> javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
>        at
> javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>        at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applicat=
ionFilterChain.java:252)
>        at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilte=
rChain.java:173)
>
> ***
>
> Sorry for this very long mail but we have very interested in know more ab=
out
> thoses issues.
>
> Cordially,
>
> Laurent CELLA.
> Inexbee Software.
>


--=20
Davanum Srinivas : http://wso2.com/blogs/