Re: xsd:String encoded with zero at the end...

[Dennis Sosnoski]

From a quick look through the code there doesn't appear to be anywhere that even trys to check for valid characters - XMLUtils.xmlEncodeString() just handles encoding special characters, and SimpleSerializer.getValueAsString() just calls toString(). There should definitely be a check for valid characters in a String value. The best place to put this might be in SimpleSerializer, since the checking only needs to be done for String values (ints, floats, etc. cannot have illegal XML characters in their String representations, so there's no need to add overhead for checking these).

- Dennis

Dennis M. Sosnoski
Sosnoski Software Solutions, Inc.
http://www.sosnoski.com

Steve Loughran wrote:

----- Original Message -----
From: "Chris Schaefer" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, December 18, 2002 08:45
Subject: xsd:String encoded with zero at the end...

I'm having a weird problem where my service returns strings which are
zero terminated ( like C ), but
actually _IN_ the XML.

The client side parser complains of invalid XML characters.

That's because zero bytes are invalid XML characters. If it did anything
other than complain, it would not be following the XML spec:

Char ::= #x9 | #xA | #xD | [#x20-#xD7FF] | [#xE000-#xFFFD] |
[#x10000-#x10FFFF]

I'm guessing this is an issue in

org.apache.axis.encoding.ser.BeanSerializer

There is certainly something going awry with whatever is putting the data on
the wire.

Anybody have a clue, or seen this before?

no. Where is the data coming from? How are zero bytes getting onto the ends
of strings? Are they coming from a database or something?

I suspect that the 00 is getting into the strings from some external source,
and because java can have nulls in strings (its not the terminator), it is
getting put on the wire.