abdera-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From James M Snell <jasn...@gmail.com>
Subject Re: [jira] Created: (ABDERA-61) Invalid byte 2 of 3-byte UTF-8 sequence
Date Wed, 05 Sep 2007 17:18:22 GMT
Hmmm...  notice that in your "ethereal stream 2", you're using chunked
requests, release 0.2.2 and you did not capture the actual bits of the
xml in the post.  Would it be possible for you to capture another trace
that includes the xml of the post?  Also, would it be possible for you
to capture the hex output.  I want to see what bytes are actually being
written to the wire.

- James

herbert welker (JIRA) wrote:
> Invalid byte 2 of 3-byte UTF-8 sequence
> ---------------------------------------
> 
>                  Key: ABDERA-61
>                  URL: https://issues.apache.org/jira/browse/ABDERA-61
>              Project: Abdera
>           Issue Type: Bug
>     Affects Versions: 0.2.2, 0.3.0
>          Environment: The System runs a RAD 7.0.0.3 on Windows XP Professional
> The JDK is:
> C:\Programme\IBM\SDP70\jdk\bin>java -version
> java version "1.5.0"
> Java(TM) 2 Runtime Environment, Standard Edition (build pwi32devifx-20070323 (if
> ix 117674: SR4 + 116644 + 114941 + 116110 + 114881))
> IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 Windows XP x86-32 j9vmwi3223ifx-2007
> 0323 (JIT enabled)
> J9VM - 20070322_12058_lHdSMR
> JIT  - 20070109_1805ifx3_r8
> GC   - WASIFIX_2007)
> JCL  - 20070131
> 
> But the program runs under JDK-Compliance-Level-1.4
> 
> The Lotus-Connections-Server runs on a WebSphere 6.1.0.9 on a Windows XP Professional
System.
>             Reporter: herbert welker
> 
> 
> When trying to create an Atom-Entry with the abdera-0.22-client on a Lotus-Connections-Server,
the server (Lotus-Connections-1.0.1) responds with a HTTP-400-Error-message:
> 
> org.xml.sax.SAXParseException: Invalid byte 2 of 3-byte UTF-8 sequence.
> 
> Some googleing gives "...The most likely cause is that the document you are uploading
specifies that it is in UTF-8 encoding, but that it contains non-UTF-8 characters. As UTF-8
is the default character set for XML, it might also be the case that the document does not
specify a character set at all."
> 
> More description and the java-code of my client is given in the attached files.
> 

Mime
View raw message