RE: Does nobody care about this stuff?

[Deane Sloan <De...@equinox.co.nz>]

>>I have gotten no response to my message from yesterday, and little from my

>>earlier messages.  Does nobody care about this stuff?  I find it hard to 
>>believe that everybody is happy with a SOAP implementation that cannot 
>>even transport accented Latin characters.
A starting point ...

org.apache.soap.util.xml.Utils.cleanString(, as used from within
SOAPMappingRegistry.java (line 187 of rev. 1.14, line 239 or rev. 1.17), the
function's interpretation and recognition of "<![CDATA[" may be unwanted and
incorrect in this context.
At this point of the serialization, one should simply encode the 5
proscribed XML characters... maybe also chars >= 128? 

I've seen posts claiming that Apache SOAP doesn't correctly handle various
forms of line feed/new lines - maybe in this context the additional
behaviour of the getSafeString function should be examined...

Best Regards,

Deane Sloan


-----Original Message-----
From: Mike Spreitzer [mailto:mspreitz@us.ibm.com]
Sent: Friday, 27 April 2001 09:02
To: soap-dev@xml.apache.org
Subject: Does nobody care about this stuff?


I have gotten no response to my message from yesterday, and little from my 
earlier messages.  Does nobody care about this stuff?  I find it hard to 
believe that everybody is happy with a SOAP implementation that cannot 
even transport accented Latin characters.
*************************************************************************
Please respond to soap-dev@xml.apache.org 
To:     soap-dev@xml.apache.org
cc: 
Subject:        Current SOAP and Xerces 1.2.2 can NOT transport a String
containing 
arbitrary Unicode characters



I've tried the April 24 nightly build of Apache SOAP, with Xerces 1.2.2,
and both problems reported below are still present.
****************************************************************************
***********
Please respond to soap-dev@xml.apache.org
To:     soap-user@xml.apache.org
cc:     soap-dev@xml.apache.org
Subject:        Re: Can SOAP 2.1 and Xerces 1.2.2 transport a String 
containing an
arbitrary Unicode character?



I used tcpdump to capture traffic containing three interesting call
messages, containing (respectively) the Strings: "qqq\u00F6zzz",
"qqq<![CDATA[zzz", and "qqq\u2030zzz" (in Java source notation) among the
data being sent.

The tcpdump output shows: (1) where \u00F6 goes, a single 00 byte was
sent; (2) the CDATA start tag was sent without being quoted; and (3) the
\u2030 was sent correctly.

Unhappily,
Mike