"Perhaps the server side can change the encoding to UTF-16?"
We suggested this (and other things) to them, but I think they are having
difficulties change encoding in some place between their db and ws server.
"having looked around a bit I guess the encoding of the SOAP-response is not
UTF-8 at a
Wesley,
Maybe you should ask this question on the Woodstox list (Woodstox is
the XML parser used by default by Axis2). It could be that there is a
way to tell the parser to ignore invalid UTF-8 sequences.
Andreas
On Mon, Dec 1, 2008 at 18:09, Wesley Mesquita <[EMAIL PROTECTED]> wrote:
> Hi all,
Wolfgang
--- On Mon, 12/1/08, Wesley Mesquita <[EMAIL PROTECTED]> wrote:
> From: Wesley Mesquita <[EMAIL PROTECTED]>
> Subject: Is there any workaround over invalid character in responses?
> To: axis-dev@ws.apache.org
> Date: Monday, December 1, 2008, 6:09 PM
> Hi all,
>
<[EMAIL PROTECTED]> wrote:
> From: Wesley Mesquita <[EMAIL PROTECTED]>
> Subject: Is there any workaround over invalid character in responses?
> To: axis-dev@ws.apache.org
> Date: Monday, December 1, 2008, 6:09 PM
> Hi all,
>
> I am havin
Hi all,
I am having troubles with the the exception:
org.apache.axiom.om.OMException: com.ctc.wstx.exc.WstxIOException: Invalid
UTF-8
middle byte 0x64 (at char #538, byte #127)
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.jav
a:239)
at
org.apache.axiom.om.
